URL Parser
Split any URL into parts with query parameters decoded into a table.
About this parser
Paste a URL; read its anatomy โ protocol, host, port (with defaults labelled), path, fragment, origin โ and every query parameter decoded into a table, %20s turned back into spaces. Click anything to copy it. The URL is parsed with the browser's own machinery and never visited.
Reading URLs defensively
The skill this tool supports is looking before clicking. The host is the only part that says where a link really goes โ and phishing lives in the gap between what a link says and where it points, with tricks like paypal.com.evil.example (the real domain is always the LAST dot-separated parts before the path). Query strings are where tracking rides: utm_ parameters, click IDs, and sometimes personal data that shouldn't be there โ decoding them shows what you'd actually be sending. Monster redirect URLs often carry their true destination inside a parameter, which the decoded table exposes without any clicking. Build clean campaign links with the UTM builder; encode and decode raw strings with the URL encoder.
Frequently asked questions
What are the parts of a URL?
Protocol (https), host (example.com), optional port, path (/page), query (?key=value pairs) and fragment (#section). The parser labels each, with default ports named.
How can I tell where a link really goes?
Read the host โ specifically the last two or three dot-separated labels before the first slash. paypal.com.evil.example belongs to evil.example, not PayPal; that gap is most phishing in one sentence.
What is percent-encoding (%20)?
URLs can't contain spaces and certain characters, so they're encoded as % plus hex โ %20 is a space. The parameter table decodes them back to readable text.
Is the URL I paste visited or logged?
Neither โ it's parsed as text in your browser and never requested. Safe for inspecting suspicious links.