URL Parser
Breaks a link into scheme, host, port, path, query parameters and fragment.
Results
What this tool does
A long URL with eight tracking parameters is hard to read and harder to reason about. Splitting it apart shows what is actually in there: which host it points at, how deep the path goes, and every query parameter listed one per line with its value already decoded. The parsing follows RFC 3986, so it handles user information, non-standard ports and IPv6 hosts in brackets.
Formula
splits the address into scheme, host, port, path, query and fragment
Variables
| Symbol | Meaning | Unit |
|---|---|---|
text | Address | — |
OUT | The parts of the address | — |
SC | Scheme | — |
HO | Host | — |
PA | Path | — |
PR | Parameters | — |
NP | Query parameters | — |
SG | Path segments | — |
Worked example
- Addresshttps://paritian.com/en/tools/?q=json&page=2#topo
- The parts of the addressscheme: https host: paritian.com port: — path: /en/tools/ query: q=json&page=2 fragment: topo
- Schemehttps
- Hostparitian.com
- Path/en/tools/
- Parametersq = json page = 2
- Query parameters2
- Path segments2
Limitations
- The calculation runs entirely in your browser. The values you type are never sent to a server.
Frequently asked questions
Does the fragment reach the server?
No, and that is a genuinely useful thing to know. Everything after the hash stays in the browser: it is never put into the request, never appears in a server log, and never reaches an analytics tool that reads the server side. That makes it the right place for something that should not travel, and the wrong place for anything the server needs to act on.