IPv4 Private Address Ranges Regex for PHP
/^(?:10\.(?:(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){2}(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])|172\.(?:1[6-9]|2[0-9]|3[01])\.(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])|192\.168\.(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))$/What this pattern does
This page provides a comprehensive, battle-tested regular expression for matching ipv4 private address ranges, ported and verified for PHP. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your PHP project — whether you're validating in a Laravel validator, a WordPress plugin, or a standalone PHP script.
Php Implementation
<?php
// IPv4 Private Address Ranges
// ReDoS-safe | RegexVault — Web & Network > IPv4
define('IPV4_PRIVATE_ADDRESS_RANGES_PATTERN', '/^(?:10\.(?:(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){2}(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])|172\.(?:1[6-9]|2[0-9]|3[01])\.(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])|192\.168\.(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))$/');
function validate_ipv4_private_address_ranges(string $input): bool {
return (bool) preg_match(IPV4_PRIVATE_ADDRESS_RANGES_PATTERN, $input);
}
// Example
var_dump(validate_ipv4_private_address_ranges("10.0.0.1")); // bool(true)Test Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
10.0.0.1 | 11.0.0.1 |
10.255.255.255 | 172.15.0.1 |
172.16.0.1 | 172.32.0.1 |
172.31.255.255 | 192.169.0.1 |
192.168.0.1 | 8.8.8.8 |
When to use this pattern
This pattern is drawn from the Web & Network > IPv4 category and carries a ReDoS-safe certification. That matters for PHP developers because especially relevant in PHP where PCRE backtracking limits can trigger silent failures on malicious input. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.
Common Pitfalls
172.16–31 is commonly written incorrectly as 172.(16-31) or 172.1[6-9|2[0-9]|31 — missing the 30 or mishandling the range.
Technical Notes
172.x range uses 1[6-9]|2[0-9]|3[01] to cover exactly 16–31. Three distinct top-level alternations for each private block — no shared suffix, which prevents backtracking.
Have a pattern that belongs in the vault?
Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.
Submit a Pattern