URL Parser
Break a URL down into its protocol, hostname, port, path, query parameters, and fragment, instantly in your browser. Debug a tracking link, inspect an API endpoint, or compare two similar-looking URLs to spot a redirect bug, with no data sent to a server.
Examples
Debugging a tracking link
Paste in a marketing or analytics URL to see every UTM parameter broken out into its own row, so you can spot a wrong or missing value at a glance.
Inspecting an API endpoint
Parse a REST API URL to quickly confirm the host, port, and path are correct, and review each query parameter without scanning a long raw string.
Checking a URL with credentials
Some legacy links embed a username and password directly in the URL. This tool pulls them out separately so you can confirm or remove them safely.
Confirming which port a service is actually listening on
Paste a URL like http://localhost:3000/api/health to immediately see the parsed port, rather than scanning a long string by eye.
Comparing two similar-looking URLs for a redirect bug
Parse both the expected and the actual redirect target side by side to spot a subtle difference in path, trailing slash, or query parameters.
Quick reference
| URL | Protocol | Hostname | Port | Path | Query string | Hash / fragment |
|---|---|---|---|---|---|---|
| https://user:pass@example.com:8080/path/to/page?query=1&lang=en#section | https: | example.com | 8080 | /path/to/page | ?query=1&lang=en | #section |
| https://example.com:443/ | https: | example.com | default | / | none | none |
| http://example.com:80/index.html | http: | example.com | default | /index.html | none | none |
| https://www.example.com/search?q=url+parser&page=2 | https: | www.example.com | default | /search | ?q=url+parser&page=2 | none |
| example.com/docs | https: | example.com | default | /docs | none | none |
| https://münchen.de/ | https: | xn--mnchen-3ya.de | default | / | none | none |
| https://[2001:db8::1]:8443/api/v1 | https: | [2001:db8::1] | 8443 | /api/v1 | none | none |
| http://192.168.0.1/admin | http: | 192.168.0.1 | default | /admin | none | none |
| https://example.com/a/../b/./c | https: | example.com | default | /b/c | none | none |
| https://example.com/path with spaces | https: | example.com | default | /path%20with%20spaces | none | none |
| ftp://ftp.example.com/pub/file.txt | ftp: | ftp.example.com | default | /pub/file.txt | none | none |
| mailto:someone@example.com | mailto: | none | default | someone@example.com | none | none |
| file:///C:/Users/me/report.pdf | file: | none | default | /C:/Users/me/report.pdf | none | none |
Frequently asked questions
What do protocol, hostname, and path mean?
The protocol (e.g. "https:") defines how the browser connects; the hostname is the domain or IP address being contacted; and the path is the location of a specific resource on that host, such as "/path/to/page".
What's the difference between the query string and query parameters?
The query string is the raw text after the "?" in a URL, such as "foo=bar&baz=qux". Query parameters are that same text split into individual key-value pairs, which this tool lists in a table for easier reading.
What is the hash or fragment used for?
The hash (the part after "#") usually points to a specific section of a page, like a heading anchor, or is used by client-side apps to store state. It's never sent to the server as part of the request.
Is it safe to paste a URL with sensitive tokens or passwords here?
Yes. This tool runs entirely in your browser using JavaScript's built-in URL parser. Nothing you type is sent to any server, logged, or stored remotely, so it's safe to inspect URLs containing API keys, session tokens, or credentials.
Why does the port show as "default" when I didn't type one?
Every protocol has a standard port even when it's omitted from the URL — 443 for https and 80 for http, for example. When no explicit port is written, this tool shows that implied default instead of leaving the field blank.
Why was "https://" added to my input automatically?
JavaScript's URL parser requires a protocol to interpret a string as a URL at all. If you paste something like "example.com/path" without one, this tool assumes https:// so it can still parse the rest, and it shows a notice when that happens. Your original text isn't modified.
Are query parameter keys and values shown decoded or still percent-encoded?
They're shown decoded, so a value like "hello%20world" in the query string appears as "hello world" in the parameters table, making it easier to read at a glance while the raw query string field still shows the original encoded form.