URL Parser
Paste a URL and see every part of it laid out: scheme, user name and password, host and port, path and its segments, each query parameter decoded, and the fragment. The parser is the same one your browser uses, so the result shows exactly how browsers read the address, including normalisation, internationalised domain names and default ports.
- Runs in your browser
- No sign-up
- Free to use
Parsed in your browser with the same parser browsers use. Nothing is requested from the address.
Parts
Host
Path segments
| # | Name | Value (decoded) | As written |
|---|
How to use URL Parser
- Paste a URL. A bare domain is read as https.
- Read the parts and the host details.
- Check the decoded query parameters.
- Review the notes on credentials, encryption and repeated parameters.
URL Parser features
All components
Scheme, credentials, host, port, path, query, fragment and origin.
Host details
Registrable domain, subdomain, top-level domain and Unicode form of IDNs.
Decoded parameters
Each query parameter decoded, alongside the original text.
Path segments
Decoded list of the path’s parts.
Warnings
Embedded passwords, plain http, script URLs, repeated parameters, tracking codes.
Private
No request is made to the address.
When to use URL Parser
- Debugging links with complicated query strings.
- Checking a suspicious link before clicking it.
- Finding which parameters a tracking link carries.
- Understanding URL structure while building routes.
URL Parser FAQ
Does the tool visit the URL?
No. It only analyses the text. No request is sent to the address.
Why does the normalised URL differ from mine?
Browsers normalise URLs: they lower-case the scheme and host, remove default ports, encode spaces and some characters, and resolve dot segments. The normalised form is what a browser would actually request.
What is the registrable domain?
The part someone registered, such as example.co.uk in shop.example.co.uk. The tool uses common rules for country domains; for a complete answer, the Public Suffix List is the authority.
What does the Unicode form mean?
Domain names with non-Latin characters are transmitted in an ASCII form starting with xn--. The tool converts it back so you can read it, which helps spot look-alike domains.
Why warn about passwords in URLs?
A URL with user:password@ exposes the password to anyone who sees the link, in browser history, logs and referrer headers.
Can a parameter appear more than once?
Yes. Some servers read the first value, some the last, some all of them as a list.
Anatomy of a URL
A URL packs several pieces of information into one line. The scheme says how to fetch the resource; the authority names the host, optionally with user information and a port; the path identifies the resource on that host; the query carries parameters; and the fragment points to a part of the page and is never sent to the server.
Reading a long URL by eye is error-prone, especially when it is full of percent-encoded characters and repeated parameters. Splitting it with a real parser shows precisely what a browser will request, which matters when debugging redirects, analytics links or API calls.
The host deserves particular attention when judging whether a link is safe. What matters is the registrable domain at the right-hand end: login.example.com.evil.net belongs to evil.net. Internationalised names can contain characters that look like Latin letters; showing the Unicode form next to the ASCII form makes such tricks easier to notice.
Query parameters are where most of a URL’s variety lies. Tracking parameters, filters, pagination and session identifiers all live here. Decoding them, and seeing which appear more than once, is usually the first step in understanding what a link actually does.