URL Parser

An absolute URL with a scheme, such as https://example.com. Relative paths like /about have no host, so the parser cannot resolve them on their own and shows an error asking for a scheme.

Hostname is just the domain, like example.com. Host includes the port when one is present, like example.com:8080. When there is no explicit port, host and hostname read the same and the Port row is empty.

Each key becomes its own row, so a=1&a=2 shows two entries. The original order is preserved and every value is kept, which matters for APIs that read multiple values for the same key.

Yes. Parameter keys and values are shown decoded, so %20 appears as a space and other escapes are resolved. A plus sign in a query is also read as a space, matching how form data is encoded.

Yes. Any scheme the URL standard accepts will parse. Some schemes like mailto do not use a host, so the Host and Hostname rows may be empty while the Pathname holds the address or resource.

Origin is the scheme plus the host and port, for example https://example.com:8080. Browsers use it as the security boundary for same-origin checks, so it is handy when debugging CORS or cookie scope.

Yes. If the URL contains userinfo like user:pass@host, both are extracted into their own rows. Putting credentials in a URL is discouraged, but the parser surfaces them so you can spot and remove them.

The URL engine normalizes non-ASCII hostnames to their punycode form, so a Unicode domain shows as an xn-- label. That is the same value browsers and DNS actually resolve.

No. Parsing happens entirely in your browser using the standard URL engine, and nothing is uploaded. Even a link with tokens or credentials stays on your device.