URL parser
Paste a URL and see every structural component — protocol, subdomain, domain, port, path, query parameters as a table, and fragment.
Anatomy of a URL
Every URL follows the same grammar: scheme://subdomain.domain.tld:port/path?query#fragment. The scheme says how to connect, the host says where, the path says what, the query carries key-value data, and the fragment points inside the page — it never reaches the server.
Debugging query strings
Long URLs from ad platforms and redirect chains hide their parameters in a wall of & and %. Parsing them into a table shows exactly what each key carries — useful for verifying campaign tags, spotting tracking parameters, and debugging OAuth callbacks.
Frequently asked questions
- What are the parts of a URL?
- A URL has up to seven parts: scheme (https), host (subdomain + domain + TLD), port, path, query string, and fragment. In https://blog.example.com:8080/articles?sort=new#top, each component serves a distinct routing or data-passing job.
- Why does the parser split co.uk as the TLD?
- Because co.uk is a public suffix — the level under which domains are actually registered. Naive parsers that treat only .uk as the suffix mis-identify example as a subdomain; this parser recognizes common two-level suffixes like co.uk, com.au, and co.jp.
- Is the fragment (#section) sent to the server?
- No. The fragment is processed entirely by the browser, which is why it never appears in server logs and why single-page apps historically used it for client-side routing.