Skip to content

SEO & Web

URL Parser & Inspector

Split any URL into its components — protocol, host, port, path, query parameters, and fragment — with every parameter decoded.

Parsed with the browser URL API — the same WHATWG rules every modern browser uses.

The Parts People Get Wrong

  • Everything after the first "#" is the fragment — it never reaches the server, which is why single-page apps can read it but server logs cannot.
  • A URL like example.com/page?q=1?q=2 has one query string; the second "?" is just part of the value until you look at it parsed.
  • The port is part of the authority: https:// implies 443, and omitting it hides the fact that a nonstandard port is in play.
  • Percent-encoded characters are decoded for display here — %2F in a path segment is a literal slash inside that segment, not a path separator.

How the Generator Works

  1. Paste a complete URL, however long or encoded.
  2. The parser breaks it into protocol, hostname, port, path, query string, and fragment.
  3. Every query parameter is listed decoded, so %20 strings become readable values.
  4. The hostname is further broken into subdomain, domain, and TLD for quick inspection.
Formula & Technical Standard
Uses the browser URL API — the same WHATWG parsing rules as every modern browser.

Example Output

Debug a tracking URL
Input: https://shop.com/s?k=laptop&ref=amazon&tag=x-20
Output: Parameter table: k=laptop, ref=amazon, tag=x-20
Each parameter on its own row makes it easy to audit affiliate or analytics parameters.

Common Questions

Can it handle non-standard protocols?

Yes — the parser accepts any scheme (ftp:, mailto:, custom app schemes) and reports the components the scheme defines.

What is the difference between path and query?

The path (/products/list) identifies the resource; the query (?color=red) carries parameters. Servers route on path and read parameters from query.