Break down any URL into its components: protocol, host, path, query parameters, hash, and port.
Paste a URL and get every piece labeled: protocol, username and password if present, host, port, path, query string, and hash. The parser applies the WHATWG URL rules that browsers use, so this is not a naive string split: hosts are lowercased, default ports disappear, and disallowed characters such as spaces come back percent-encoded (%20). The usual surprise is that the result can differ from what you pasted, and that query values are reported raw - a + stays a + and %20 stays %20 unless you decode them yourself. The whole parse runs in your browser, so the URL never leaves your machine.
A concrete input and expected output from the current implementation.
Input
https://user:pass@example.com:8080/path/to/page?q=hello+world&lang=en#section-2
Expected output
Protocol: https Username: user Password: pass Host: example.com Port: 8080 Path: /path/to/page Query: q=hello+world&lang=en q = hello+world lang = en Hash: section-2
The structural markers are read left to right: userinfo closes at @, the port stays 8080 because it differs from https's default (443), the path begins at the first / after the host, ? opens the query, # opens the fragment, and the query splits into two key=value pairs. Plus signs are left alone because only form encoding turns + into a space.
Components are cut at structural markers: the first colon ends the scheme, // opens the authority section, @ closes the username and password pair, a second colon marks the port, the first / starts the path, ? starts the query, and # starts the fragment. A character's role depends on position - a colon appears in the scheme, in userinfo, and in the port.
The URL standard defines a canonical form, and the parser applies it: hostnames are lowercased, non-ASCII hosts are encoded as punycode (münchen.de becomes xn--mnchen-3ya.de), ports equal to the scheme default are removed (80 for http, 443 for https), and spaces or non-ASCII characters in path, query, or fragment become percent-encoded UTF-8 (%20, %C3%A9). What you pasted and what the tool reports can therefore differ.
Because 443 is the default port for https. The URL standard removes a port that matches its scheme's default while parsing, and the same happens to :80 on http and :443 on wss. A port survives only when it differs from the default, which is why 8080 appears in the example output and 443 would not. Requests to the default port are identical to requests without one.
Your host contains a non-ASCII letter, and the URL standard encodes internationalized domain names as punycode during parsing: each non-ASCII label is transformed and prefixed with xn--, so münchen.de becomes xn--mnchen-3ya.de. That encoded form is exactly what DNS sees; browsers display the decoded name only as a convenience. The encoding is defined in RFC 3492.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.