Docker Port Mapping Regex for PHP
/^(?:(?:(?:(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]):)?(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3}):)?(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3})(?:/(tcp|udp|sctp))?$/iWhat this pattern does
This page provides a comprehensive, battle-tested regular expression for matching docker port mapping, 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
// Docker Port Mapping
// ReDoS-safe | RegexVault — Dev & Systems > Docker
define('DOCKER_PORT_MAPPING_PATTERN', '/^(?:(?:(?:(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]):)?(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3}):)?(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3})(?:\/(tcp|udp|sctp))?$/');
function validate_docker_port_mapping(string $input): bool {
return (bool) preg_match(DOCKER_PORT_MAPPING_PATTERN, $input);
}
// Example
var_dump(validate_docker_port_mapping("8080:80")); // bool(true)Test Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
8080:80 | 0:80 |
127.0.0.1:8080:80 | 8080:0 |
0.0.0.0:443:443 | 99999:80 |
80 | 8080:99999 |
8080:80/tcp | host:80:80 |
3000:3000/udp | 8080:80/http |
When to use this pattern
This pattern is drawn from the Dev & Systems > Docker 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
Publishing 0.0.0.0:port exposes services on all interfaces including public ones. Always bind to 127.0.0.1 for development services unless public access is intentional.
Technical Notes
Protocol defaults to tcp. Exposing on 0.0.0.0 (all interfaces) is the default. Use 127.0.0.1 to restrict to localhost for development services.
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