Free · live registry data · no login

URL Parser

Break a URL into scheme, host, path and query.

How it works

Break any URL into scheme, host, port, path, query and fragment

Paste a long, messy link and see every part laid out: protocol, subdomain, registered domain and TLD, port, each path segment, every query parameter decoded into a table, and the fragment. We flag the things that bite in practice: tracking parameters bloating the link, credentials embedded in the URL, plain http, internationalised hosts that browsers show as xn--, and double-encoded values. Then we hand you a clean, canonical version of the link to share.

Results appear here after you click Parse URL.

How this works

1
Parse with the WHATWG algorithm
The same URL parser browsers use splits the link into scheme, userinfo, host, port, path, query and fragment.
2
Decode and classify
Path segments and query values are percent-decoded; parameters are tagged as tracking, numbers or text.
3
Check and clean
A live DNS lookup confirms the host exists, and we rebuild a canonical link without tracking or credentials.

Frequently asked questions

What are the parts of a URL?: A URL has a scheme (https), optional userinfo, a host (the domain or IP), an optional port, a path (/products/shoes), an optional query string (?color=red&size=42) and an optional fragment (#reviews). The host is the only part that involves DNS; everything after it is interpreted by the web server or the page.
What is the difference between a domain, a hostname and a URL?: The domain is the name you register (example.com). A hostname is any name that resolves in DNS, including subdomains like shop.example.com. A URL is the full address of one resource, combining a hostname with scheme, path and query.
Is the part after # sent to the server?: No. The fragment stays in the browser and is used to jump to a section or by single-page apps for routing. Servers, analytics logs and redirects never see it, which is why tracking parameters go in the query string instead.
Should I remove utm_ parameters from links I share?: Keep them in campaign links you control (email, ads, social posts) so analytics can attribute visits. Strip them from links you forward to people or embed in documents, because they misattribute traffic and make links long and ugly.
Why does my URL show %20 and other percent codes?: Characters that are not allowed raw in a URL, such as spaces, accents and &, are percent-encoded as their UTF-8 bytes (space becomes %20). Browsers decode them for display. If you see %2520, the value was encoded twice and the server will probably receive a literal %20.

Every MailShrine domain includes WHOIS privacy, transfer lock, Anycast DNS with DNSSEC and two business mailboxes.