URL Parser & Query String Editor

Parsing uses the WHATWG URL Standard implementation built into your browser — the same code that resolves links on web pages — so the results match what new URL() returns in JavaScript and Node.js. That includes normalisation: the scheme and host are lower-cased, default ports such as :443 are dropped, and .. segments are resolved.

Internationalised domain names are converted to punycode (münchen.example becomes xn--mnchen-3ya.example), which is what DNS actually resolves; the Unicode form is shown alongside. Paths and fragments are also shown percent-decoded, so caf%C3%A9 reads as café.

Query parameters are read with URLSearchParams, which follows application/x-www-form-urlencoded rules: + means a space and repeated keys such as tag=a&tag=b are kept as separate rows. When you edit the table, the query string is re-encoded the same way. Relative URLs are resolved against https://example.com so you can still inspect them. Credentials in the userinfo part (user:pass@) are shown separately because browsers strip or warn about them, and they should never appear in shared links.