URL parser

Breaks a URL down into its scheme, host, port, path and query parameters.

Parse a URL into its separate constituent parts (protocol, origin, params, port, username-password, ...)

Steps and notes

What is URL parser?

This tool applies the browser's native URL parser to whatever you paste and lays out every component the spec recognizes: protocol, username, password, hostname, port, pathname, query parameters (each key and value on its own row) and fragment. Using the same parser as the browser matters because URL edge cases are genuinely subtle — default ports are hidden, percent-encoding is normalized, and internationalized domain names are converted to punycode. When a redirect, an allowlist check or a routing rule is not behaving as expected, parse the exact string here first; the discrepancy between what you think the URL is and what the parser sees is usually the bug.

  1. Paste the full URL
  2. Read the parsed fields
  3. Query parameters are listed as a table for easy copying

Frequently asked questions

Why is the port missing from my parsed URL?
Default ports are not written in URLs: https implies 443 and http implies 80, and the browser's parser reports an empty port for them. The URL is not "missing" anything — the scheme determines the port automatically.
Can a URL with a username and password be safe?
Basic-auth credentials in a URL (https://user:pass@host) are visible in logs, browser history and Referer headers, and several browsers now strip or block them. The parser shows them so you can audit links — production systems should send credentials via headers instead.
What does the #fragment part mean for the server?
Nothing: the fragment is never sent to the server, it stays in the browser (for anchor jumps or, in SPA frameworks, as client-side routing). Two URLs differing only in fragment are the same request to a server.

Read the full step-by-step guide for this tool

Category: Web

URL & encoding workflow

URL Encoder & Decoder — Percent-Encoding, encodeURIComponent Pitfalls → URL parser → Outlook SafeLink Decoder → Slugify string → Escape HTML entities

Read next