Forwarded Header Parser

Standard Forwarded Header

Parse RFC 7239 Forwarded proxy chain and view the value of for / by / host / proto at each hop.

Hop #1
for203.0.113.43
protohttps
hostapp.geekformat.com
Hop #2
for10.0.0.9
byingress

X-Forwarded-* Compatible Headers

Many gateways still use X-Forwarded-For / Host / Proto. This parses the client and proxy addresses in chain order.

2 X-Forwarded-For node(s)These headers are only meaningful in a trusted proxy chain and should not be treated as the real client IP.
#1203.0.113.43
#210.0.0.9

JSON Preview

{
  "standardized": [
    {
      "index": 0,
      "pairs": {
        "for": "203.0.113.43",
        "proto": "https",
        "host": "app.geekformat.com"
      }
    },
    {
      "index": 1,
      "pairs": {
        "for": "10.0.0.9",
        "by": "ingress"
      }
    }
  ],
  "legacy": {
    "x-forwarded-for": [
      "203.0.113.43, 10.0.0.9"
    ],
    "x-forwarded-proto": [
      "https"
    ],
    "x-forwarded-host": [
      "app.geekformat.com"
    ]
  }
}

Parse proxy headers online and understand your real source and forwarding order first.

Related

Content-Disposition Parser

💡 Popular in network toolkit

CORS Inspector

CSP Generator

HTTP Cookie Parser

Time Tools

Meta Tag Generator

Use Cases

  • When the backend receives incorrect client IPs, parse Forwarded and X-Forwarded-For headers to trace the issue
  • Analyze the order of CDN, Nginx, gateway, and other proxy nodes to confirm the forwarding path
  • Debug reverse proxy configurations to verify Host and Proto passthrough and prevent protocol downgrade
  • Investigate header rewriting or loss in multi-proxy environments and copy parsed results for support tickets

How to Use

  1. Paste Forwarded, X-Forwarded-For, X-Forwarded-Host, or X-Forwarded-Proto header values
  2. The tool automatically parses the proxy chain, real IP, Host, and Proto fields with structured output
  3. Review proxy node order and protocol transformation to verify the forwarding path matches expectations
  4. Copy parsed results for support tickets, log analysis, or debugging documentation

Features

  • Multi-layer proxy chain visualization: See who forwarded to whom and how protocols change at a glance
  • More reliable source IP detection: Ideal for CDN, gateway, reverse proxy, and multi-tier proxy troubleshooting
  • Gateway and CDN friendly: Built for Nginx, Ingress, reverse proxy, CDN, and API gateway issue diagnosis
  • Structured result display: Fields are broken down clearly for easy copying into tickets, log analysis, and debugging records

FAQ

How can I see which proxy nodes a request passed through?

Paste the relevant headers and you'll see the proxy chain order and each hop's details. Perfect for troubleshooting lost real IPs or protocol misidentification.

Why does the backend see the wrong client IP?

Common causes include proxy layers not passing through headers, gateways overwriting them, or multiple CDN/reverse proxy layers stacking. Parsing these headers helps identify where the IP was modified.

Is this suitable for debugging Nginx, Ingress, API Gateway, and CDN issues?

Absolutely. Especially when origin paths are complex and requests traverse multiple proxies, structured header viewing significantly speeds up troubleshooting.

What information can I see besides the IP?

Beyond source IP, you can also inspect Host, Proto, by, and other fields to verify protocol conversion, domain passthrough, and proxy behavior match expectations.