Is the URL I paste sent to your server?

No. Parsing uses the browser's native URL API and runs entirely on your device. The URL is never transmitted or fetched — the tool inspects the string, it does not visit the address.

What is the difference between host and hostname?

Hostname is just the domain (example.com), while host includes the port when one is explicitly present (example.com:8080). If the URL uses the protocol's default port, host and hostname are identical and Port shows "(default)".

Are query parameters percent-decoded?

Yes. Parameters are read via URLSearchParams, so keys and values in the table are shown decoded — %20 becomes a space, and repeated keys appear as separate rows.

URL Parser & Analyzer

Overview

This tool parses a URL with the browser’s standards-compliant URL API and lays out every component: Protocol, Host, Hostname, Port, Path, Query, Fragment, and Origin. The query string is additionally expanded into a key/value table with percent-decoding applied — useful for debugging redirects, OAuth callbacks, UTM tags, and signed URLs.

How to use

Paste a full URL into the URL field, including the scheme (e.g. https://).
Read the component breakdown in the stats list; missing parts show (default) or (none).
If the URL has a query string, inspect each pair in the Query parameters table.

Examples

https://[email protected]:8080/path?a=1&b=2#top → Protocol https:, Host example.com:8080, Port 8080, Path /path, Fragment #top, parameters a=1 and b=2.
https://example.com/search?q=hello%20world → parameter q = hello world.

Notes

Input must be an absolute URL — relative paths like /foo?bar=1 are rejected as Invalid URL because the WHATWG URL parser requires a scheme. The parser follows the same rules as fetch and the address bar, so what you see here is what your code sees.