URL Parser inspect
Break a URL into protocol, host, port, path, query parameters, and fragment.
What this tool does
A URL is several components joined by fixed rules. Short addresses are readable at a glance, but once several tracking parameters are attached and values are percent-encoded the structure becomes opaque.
This tool uses the browser built-in URL parser to split an address into its parts. Protocol, host, port, path, query, and fragment are listed separately, and query parameters are expanded into a key and value table. Encoded paths are shown decoded as well, so you can see immediately what the values actually contain.
When the port is omitted the protocol default is displayed, 443 for https and 80 for http. If the address carries credentials the username is shown while the password is masked to its length only.
When to use it
Use it to inspect tracking parameters on a campaign link, to read the code and state values delivered to an OAuth callback, to analyse addresses in a redirect chain, or to translate an example URL from documentation into code.
Input and output examples
https://example.com:8443/path/to/page?q=hello%20world&tags=a&tags=b#section
protocol https / host example.com / port 8443 / path /path/to/page / q = hello world / tags = a, b / fragment section
Encoded values are shown in decoded form.
https://example.com/search?utm_source=news&utm_medium=email
Two query parameters split into keys and values
Makes tracking parameters immediately visible.
Notes and limitations
Addresses without a scheme cannot be parsed, so example.com/path produces an error and you must include https://. Repeated query keys are listed individually, but whether a server treats them as an array or keeps only the last value differs by framework. Remember too that the fragment after # is used only inside the browser and is never sent to the server. URLs carrying credentials can persist in logs and referrer headers, so avoid pasting addresses that contain real secrets.
Frequently asked questions
Why does example.com alone fail?
The standard parser accepts absolute URLs only. Prefix the address with https://.
Can the server see the part after #?
No. The fragment stays in the browser and is not included in the HTTP request.