Anatomy of a URL
A URL packs a lot of information into a single line: a protocol, an optional username and password, a hostname, an optional port, a path, an optional query string, and an optional fragment. Each piece has meaning, and bugs frequently hide in the small details: a missing trailing slash, an unencoded ampersand in a query parameter, a port number that defaults silently.
The URL Parser breaks any URL down into its components and shows the query parameters in a sortable table with values URL-decoded for you. Because parsing uses the built-in URL constructor exposed by the browser, the output is exactly what your server-side code will see when it parses the same URL with its own standard library.
What gets parsed
- Protocol (http, https, ftp, mailto, etc.)
- Username and password (rarely used, but legal)
- Hostname and port
- Pathname
- Search / query string and individual decoded parameters
- Hash / fragment
- Origin (protocol + host + port)
Use cases
Inspect a redirect URL during OAuth debugging. Read the parameters of a long campaign-tracking link to verify your UTMs. Confirm that a webhook destination uses HTTPS. Decode a URL-encoded redirect_uri value. Compare two URLs that look the same but have different fragment or trailing slash behaviour. The tool runs locally, so even URLs containing sensitive tokens stay private.