URL Parser

Inspect the parts and repeated query parameters of an HTTP or HTTPS URL without opening it.

Processing happens in this browser. Your inputs and files are not uploaded.

Use a complete HTTP or HTTPS URL up to 16,384 characters. The result includes any credentials or tokens in your input; avoid sharing it.

Inspect a URL without visiting it

URL Parser breaks a complete HTTP or HTTPS address into its components. It does not open the destination, check whether the server exists or test whether a link is safe. This is useful when investigating query strings, redirect parameters or a copied URL with an unexpected port or fragment.

Parse an address

  1. Paste a complete URL, including https:// or http://, into Input text.
  2. Choose Parse URL.
  3. Inspect the JSON in Result, or choose Download JSON report to save it for local reference.

Choose Load example (replaces inputs) to try https://example.com:8443/docs?q=hello+world&q=tools#intro. It produces hostname example.com, port 8443, path /docs and fragment #intro. The query array keeps both q entries in order. Their decoded values are hello world and tools.

Why the output can differ from the pasted spelling

The browser URL parser normalizes the address. Hostname capitalization may change, default ports may disappear, and internationalized hostnames may appear in their ASCII form. normalizedUrl shows the resulting browser interpretation; it is not a byte-for-byte copy of the input.

Query parameters are represented as an array rather than an object so repeated names are retained. Percent escapes are decoded in query names and values, and + becomes a space through URLSearchParams. Path and fragment fields retain the browser's URL representation; this tool does not repeatedly decode nested URLs.

Credentials and tokens

The report includes username and password components if present, along with query parameters that might contain access tokens. Inputs are processed locally and no destination request is made, but downloaded reports can still contain sensitive text. Review them before sharing. Parsing an address does not establish the authenticity of its hostname or the trustworthiness of a destination.

Limits and next steps

Inputs are limited to 16,384 characters. Relative paths such as /account, missing schemes and non-HTTP schemes are rejected. A syntactically valid address can still point to an unreachable service. The parser also does not resolve short links, follow redirects, perform DNS lookups or inspect HTTP headers.

For encoding one parameter value, use URL Encoder and Decoder. If a parameter contains a three-part token you need to inspect, JWT Decoder can decode its structure; decoding does not verify its signature.