REGEXVAULTv2.0
Web & Network/HTTP
Verified Safe

X-Forwarded-For Header Value Regex for PHP

/^(?:(?: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])){3}|[0-9a-fA-F]{0,4}(?::[0-9a-fA-F]{0,4}){2,7})(?:\s*,\s*(?:(?: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])){3}|[0-9a-fA-F]{0,4}(?::[0-9a-fA-F]{0,4}){2,7}))*$/i

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching x-forwarded-for header value, 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
<?php
// X-Forwarded-For Header Value
// ReDoS-safe | RegexVault — Web & Network > HTTP

define('XFORWARDEDFOR_HEADER_VALUE_PATTERN', '/^(?:(?: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])){3}|[0-9a-fA-F]{0,4}(?::[0-9a-fA-F]{0,4}){2,7})(?:\s*,\s*(?:(?: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])){3}|[0-9a-fA-F]{0,4}(?::[0-9a-fA-F]{0,4}){2,7}))*$/');

function validate_xforwardedfor_header_value(string $input): bool {
    return (bool) preg_match(XFORWARDEDFOR_HEADER_VALUE_PATTERN, $input);
}

// Example
var_dump(validate_xforwardedfor_header_value("192.168.1.1")); // bool(true)

Test Cases

Matches (Valid)
Rejects (Invalid)
192.168.1.1not-an-ip
203.0.113.1, 192.168.1.100192.168.1.1, bad
::1, 10.0.0.1, 203.0.113.5256.0.0.1
2001:db8::1, 192.168.0.1192.168.1.1;10.0.0.1
10.0.0.1,192.168.1.1,203.0.113.1192.168.1.1,

When to use this pattern

This pattern is drawn from the Web & Network > HTTP 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

Use Forwarded: (RFC 7239) instead of X-Forwarded-For in new deployments — it is standardized and harder to spoof. Parse from the rightmost IP you trust.

Technical Notes

The leftmost IP is typically the original client, subsequent IPs are proxies. Never trust X-Forwarded-For blindly — it can be spoofed by clients. Only trust it when set by a known, controlled proxy.

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