URL Parser

Runs in your browser

Break any URL into its components — protocol, host, port, path, query and fragment — and encode or decode parts. Nothing leaves your browser.

Encode / decode

Text

How to read the results

The parser follows the WHATWG URL standard — the same logic browsers use. Origin is scheme + host + port; a URL without a special scheme may show an opaque origin. Default port indicates whether the port is implied by the scheme.

Examples

https://a.example/x?q=1#top → host a.example, path /x, query q=1, fragment #top.
https://münchen.de → Punycode host xn--mnchen-3ya.de.

Sensitive tokens in URLs

Query strings can contain secrets (session tokens, API keys). Avoid sharing full URLs that include them.

Parsing and encoding run in your browser via the native URL API. Learn about our data sources →

Frequently asked questions

Is my URL sent anywhere?

No. Parsing uses the browser’s built-in URL engine. Nothing is transmitted or logged.

Why is the password hidden?

If a URL includes credentials, we only indicate that a password is present and mask its value to avoid exposing secrets on screen.

What is Punycode?

Internationalized domain names (IDN) with non-ASCII characters are encoded to an ASCII form beginning with xn-- for DNS. We show both when applicable.