Forwarded header parse
Split comma-separated Forwarded entries and their key=value pairs.
Client#1: for=192.0.2.60, proto=https, host=example.com
Nearby workflows on Toolcore
- X-Forwarded-For parse — List client IPs from X-Forwarded-For comma chain. 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.
- 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.
- 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.
Common use cases
- Forwarded header 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.
X-Forwarded-For parse
ClientList client IPs from X-Forwarded-For comma chain.
HTTP headers
ClientCommon request and response header fields—names, direction, and short summaries—filterable client-side.
URL parser
ClientSplit URLs into protocol, host, path, query, and hash—browser URL API; optional https:// assumption; no fetch.
CIDR calculator (IPv4 & IPv6)
ClientIPv4 or IPv6 CIDR: network, range, mask or prefix size—computed locally in your browser.