X-Forwarded-For parse

Client

Left-most is original client in typical proxy chains.

About X-Forwarded-For parse

List client IPs from X-Forwarded-For comma chain. The interactive transform on this page runs in your browser tab—Toolcore does not need your paste for the core operation described above.

How to use this page

Paste or type in the main workspace, run the primary action from the toolbar, then copy or download the result. Use Load example when the page offers it, or URL prefill (?q= / ?qb=) so agents and tickets open the same input.

Client: 203.0.113.1
Proxy 1: 70.41.3.18
Proxy 2: 150.172.238.178

Nearby workflows on Toolcore

  • Forwarded header parse — Parse RFC 7239 Forwarded header directives. when headers, identifiers, or reference tables need a sibling check.
  • HTTP headers — Common request and response header fields—names, direction, and short summaries—filterable client-side. when headers, identifiers, or reference tables need a sibling check.
  • CIDR calculator (IPv4 & IPv6) — IPv4 or IPv6 CIDR: network, range, mask or prefix size—computed locally in your browser. when headers, identifiers, or reference tables need a sibling check.
  • URL parser — Split URLs into protocol, host, path, query, and hash—browser URL API; optional https:// assumption; no fetch. when headers, identifiers, or reference tables need a sibling check.

Common use cases

  • X-Forwarded-For parse for quick local checks without uploading data.
  • Copy results into tickets, docs, or classroom notes.

Common mistakes to avoid

  • Unexpected input shape

    See the intro and how-to notes for accepted formats.

FAQ

Is processing local?

Yes—this runs entirely in your browser.

Agent prefill?

Use q or qb for the main text field when supported.

More tools

Related utilities you can open in another tab—mostly client-side.