URL parser
What is an Url Parser?
Long URLs with many parameters are hard to read at a glance, especially tracking links, OAuth redirects and API calls. This parser splits a URL into its components using the same URL API that browsers use, and lists every query parameter with its decoded value.
How to use it
- Paste a full URL.
- Read each component and the decoded query parameters.
Example
Parsing https://admin:[email protected]:8443/api/v2/orders?status=open&sort=-date&q=red%20shoes#top gives:
- Protocol:
https: - Username / password:
admin/secret - Hostname:
shop.example.com; port:8443 - Origin:
https://shop.example.com:8443 - Pathname:
/api/v2/orders - Query parameters: status = open, sort = -date, q = red shoes
- Hash:
#top
Useful for
- Inspecting tracking links to see UTM and click ID parameters before clicking.
- Debugging OAuth flows, where
redirect_uri,stateandcodeparameters must match exactly. - Checking where a link really goes: in
https://[email protected]/, the real host isevil.test; the part before@is a username. This trick is used in phishing.
Notes
- Default ports (443 for HTTPS, 80 for HTTP) are shown as empty.
- Credentials in URLs are deprecated and blocked by most browsers; never put real passwords in links.
- Parsing happens locally in your browser.
Frequently Asked Questions
What is the difference between host and hostname?
Hostname is the domain only, such as example.com. Host includes the port when one is specified, such as example.com:8443.
What is a URL origin?
The combination of scheme, hostname and port. Browsers use the origin for security rules such as CORS and storage isolation.
Why is the port empty for a normal HTTPS URL?
Default ports, 443 for HTTPS and 80 for HTTP, are not shown because they are implied.
How can a URL hide its real destination?
Text before an at sign is treated as a username, so [email protected] actually points to other.test.