What parts of a URL does it show?

It breaks the URL into protocol, username, password, hostname, port, origin, path, query string, individual query parameters and the #fragment.

Why does it say the URL is invalid?

The parser needs an absolute URL with a scheme. Add https:// (or another protocol) to the front so it can be parsed correctly.

Is my URL sent to a server?

No. The URL is parsed entirely in your browser using the built-in URL API, so nothing is uploaded.

What is the difference between the host and the hostname?

The hostname is just the domain, e.g. example.com. The host includes the port if one is present, e.g. example.com:8080. The parser shows both.

What is the origin of a URL?

The origin is the scheme, hostname and port combined — for example https://example.com — and nothing more. Browsers use it for same-origin security decisions, so it omits the path, query and fragment.

Are query parameters decoded automatically?

Yes. Each parameter's value is percent-decoded as it is listed, so %20 appears as a space and %C3%A9 as é, making a long tracking URL readable.

What happens to the part after the # symbol?

That is the fragment (or hash). It is shown separately and is never sent to the server by the browser — it is used client-side for in-page anchors and single-page-app routing.

Why must I include https:// at the front?

The built-in URL parser requires an absolute URL with a scheme to resolve components unambiguously. A bare example.com/path has no protocol, so add https:// (or the relevant scheme) for it to parse.

URL Parser — Gera Tools

URL parser

Every web address packs several pieces of information into one string: the protocol, the host, an optional port, the path, a query string and a fragment. This parser splits any absolute URL into those parts using the browser’s native URL API, so the breakdown matches exactly how browsers and servers interpret the address — handy for debugging links, reading long tracking URLs, or building integrations.

How it works

The tool constructs a URL object from your input and reads its standard properties: protocol (e.g. https:), optional username and password, hostname, port, origin (scheme + host + port), pathname, search (the raw query string) and hash (the #fragment). It then walks the query string with URLSearchParams, percent-decoding each parameter, and lists the individual key–value pairs. Because the API needs an absolute URL, the input must include a scheme such as https://.

Example

Parsing https://shop.example.com:8443/products?id=42&ref=email#reviews produces:

Component	Value
Protocol	https:
Hostname	shop.example.com
Port	8443
Origin	https://shop.example.com:8443
Path	/products
Query	?id=42&ref=email
Fragment	#reviews

The query parameters are listed separately as id = 42 and ref = email.

Everything runs in your browser using the built-in URL API, and nothing is uploaded.