BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
URL Parser & Inspector
A URL parser takes any web address and splits it into the named pieces that browsers, servers, and analytics platforms actually read: protocol, hostname, port, path, query string, and fragment. Reading those parts by eye is error-prone, because a single misplaced ampersand, an encoded space, or an unexpected port can change how a redirect, a canonical tag, or a tracking link behaves. This inspector uses the browser’s own URL API, so it resolves a pasted address exactly the way a real browser would.
The tool is free and runs entirely in your browser. Paste a URL and it instantly lists every component, decodes the query parameters into a readable key and value table, and derives the registrable root domain, with a copy button on each part so nothing has to be retyped by hand.
🔒 Private: everything runs in your browser. Nothing you paste is uploaded.
How to read a parsed URL
Paste a full address into the field and every component updates instantly. If you leave the scheme off, the tool assumes https:// so a bare host still parses, and an invalid string raises a clear error pill instead of guessing.
The host, port, and root domain decide where a request lands
The hostname is the server name a browser resolves through DNS, while the port, shown only when it is explicit, picks the listening service. The registrable root domain strips subdomains down to the name plus its public suffix, which matters when you compare a canonical against its variants or check whether two links point at the same site. Multi-label suffixes such as co.uk are handled from a curated list, so a host like blog.example.co.uk correctly resolves to example.co.uk rather than the misleading example.co.
Query parameters are decoded so tracking tags are readable
Everything after the question mark is the query string, a set of key and value pairs that feed campaign tracking, pagination, filtering, and session handling. The inspector iterates the parsed parameters and decodes each key and value, turning %20 back into a space and + back into a space where the standard requires it. When the decoded value differs from what was typed, the original raw segment is shown beside it, so an over-encoded UTM tag or a double-encoded redirect target becomes obvious at a glance instead of staying hidden.
Origin, path, and fragment shape redirects and analytics
The origin combines scheme, host, and port and is the unit browsers use for same-origin security decisions and CORS. The pathname is the resource location a server routes on, and the hash fragment, which never reaches the server, often drives single-page navigation and on-page anchors. Seeing these separated makes it easier to write a redirect rule that targets the right path, confirm a canonical URL carries no stray fragment, and verify that an analytics link is not leaking a session token into a shareable address.
URL parser frequently asked questions
Q1What does a URL parser actually break a link into?
It splits an address into the components the URL standard defines: the protocol or scheme, the hostname, an optional port, the pathname, the query string with its individual parameters, and the hash fragment. This inspector also reports the origin and derives the registrable root domain. Each part is shown separately with its own copy button, so you can lift exactly the piece you need without editing the string by hand.
Q2Why decode the query parameters instead of showing them raw?
Query values are percent-encoded so that spaces, ampersands, and other characters survive transport, which makes a raw query string hard to read. Decoding turns %20 back into a space and reveals the real value of each tracking tag. When the decoded value differs from the encoded one, the tool shows the raw segment alongside it, so double-encoded redirects and malformed campaign tags are easy to spot.
Q3How does the tool work out the root domain?
It strips subdomains down to the registrable name plus its public suffix. Single-label suffixes like .com are handled directly, and common multi-label suffixes such as co.uk or com.au are matched against a curated list so a subdomain does not get mistaken for the root. This is labelled as an estimate, because the full Public Suffix List is too large to ship client-side, but it covers the suffixes most professionals encounter.
Q4What happens if I paste an invalid or incomplete URL?
If you omit the scheme, the tool assumes https:// so a bare host such as example.com/path still parses, and it notes that the scheme was assumed. If the string cannot be parsed at all, for example because it contains spaces or has no host, a red error pill appears and the breakdown is hidden until you correct it, rather than the tool inventing parts that are not there.
Q5Does this URL inspector send my links anywhere?
No. Parsing happens entirely in your browser using the native URL API, with no network request of any kind. Nothing you paste is uploaded, logged, or stored, and the tool keeps working after the page has loaded even with no connection. That makes it safe for internal staging links, signed URLs, or any address you would not want to send to a third-party server.
