URL Parser
Split any URL into scheme, host, port, path, fragment and query parameters, with automatic decoding and duplicate keys flagged.
How to Use
- Paste the URL
Drop a full address into the box and it parses as you type — the button is there to force a recompute.
- Check each part
The cards on top show scheme, host, port, origin, fragment and parameter count; the decoded path sits below.
- Audit the parameter table
Each line reads name = value, with [i/n] on repeated keys. The note underneath calls out the most noteworthy issue in the address.
FAQ
Why does 443 appear when no port was written?
That is the protocol default. The tool shows it but marks it as a default; to tell whether the address truly carries a port, look for a colon followed by digits.
What is wrong with duplicate keys?
Server implementations disagree: PHP keeps the last value by default, Node's URLSearchParams.get returns the first, and some frameworks read all of them into an array. A link with repeated keys behaves differently per backend — a real risk worth noticing.
Is the fragment sent to the server?
No. Everything after the hash stays in the browser for in-page navigation and never appears in the HTTP request, so tracking parameters placed after it do nothing.
Why can't a relative path show a host?
A relative address carries no host information at all. The tool falls back to a placeholder domain so parsing can proceed, but displays dashes for host and origin rather than inventing a fake one.