Network Tools
HTTP Status Codes
Look up what each HTTP response status code means.
Network Tools
URL Parser
Break a URL into protocol, host, path and query parameters.
Tool Panel
Processed locallyAbout URL Parser
Splits a URL into protocol, host, path, query parameters and hash, listing each parameter.
- 1
Parses with the browser's own WHATWG URL implementation — the same rules as the address bar — and lists protocol, host (with port), domain, port, path, query string, fragment and the normalised full URL at once.
- 2
The query string is **decoded item by item** below: both `+` and `%20` come back as spaces, while the raw encoding stays on the Query string row so the two can be compared.
- 3
Domains are shown in the ASCII form DNS uses, so an internationalised domain becomes punycode (`例え.jp` → `xn--r8jz45g.jp`); entering `example.com/a` gets `https://` added (switchable).
- 1
Paste a URL
With or without a scheme — auto-prefixing is on by default, and an invalid URL reports an error rather than guessing.
- 2
Check the fields row by row
When no port is written it says "default" instead of inventing 80 or 443.
- 3
Read the decoded query items
Keys and values are listed separately, which is how you debug escaping — whether a space was sent as `+` or `%20`.
Because the URL standard returns an empty port for a default one: `https://x.com` and `https://x.com:443` normalise to the same address. The row says "default" rather than guessing a number, and shows a written port verbatim.
No. The fragment is never sent to the server and gets its own row; parameters must sit after the `?`. It is a common mix-up: changing the hash does not trigger a server request, changing the query does.
Related tools
View allNetwork Tools
IP Info
See your public IP address and where it resolves to.
Network Tools
Network Tools
URL Query Builder
Assemble long query strings without escaping mistakes.
Network Tools