Domain Breakdown (TLD and Public Suffix)
WebEverything runs locally in your browser — nothing is uploaded
Take a domain apart: which label is the subdomain, which is the registered domain, whether the public suffix is co.uk or plain uk, and whether the TLD is a country code or a generic one. Country names come from the runtime's own localisation data — the same region code reads as United Kingdom in English and as its local equivalent in every other language — rather than a copied static table, which is never complete and cannot follow the interface language. Public suffixes (the co.uk, com.cn, ne.jp family) cover the common forms of thirty-odd countries, and where a country is not covered the tool says so instead of guessing. The input can be a domain, a full URL with protocol and path, or a bare TLD.
Features
- Every label gets a role: subdomain, registered domain, public suffix, TLD
- Two-level public suffixes recognised for 30+ countries (co.uk, com.cn, ne.jp, com.br …)
- TLD type: country-code, generic, or infrastructure
- Country and region names in the interface language, from the runtime ICU data
- Full URLs are reduced to their hostname — protocol, port, path and user info dropped
- IDN domains come with their Punycode form
- Where the second-level suffix is not covered, it says so rather than guessing
How to use
- Paste a domain or a full URL
- Public suffix, TLD, type and country appear as you type
- Turn on the label breakdown to see what each part does
- Copy any single line with its own button
FAQ
- What is the difference between a public suffix and a TLD?
- The TLD is the last label (uk); the public suffix is the level at which names can be registered (co.uk). Under co.uk, example.co.uk is the full name someone can register — treating co.uk as the registrable unit leads to wrong conclusions, such as assuming example.co.uk and other.co.uk belong to the same owner.
- Why are some countries not recognised?
- The full Public Suffix List runs to more than ten thousand lines and changes daily; this tool covers the common suffixes of common countries. For a country that is not covered (say .fi) it says so explicitly and treats the TLD as a single label, rather than guessing an answer that may be wrong.
- Do IDN domains work?
- Yes. Enter an IDN such as münchen.de and its Punycode form (xn--mnchen-3ya.de) is shown — that is the form DNS and certificates actually use. For a label-by-label conversion, see the Punycode converter.
- Is the domain recorded?
- No. The breakdown happens in the browser and the page sends no requests — not even an internal hostname leaves the machine.
Related tools
Punycode Converter
WebConvert internationalised domains to Punycode (xn--) and back, label by label, flagging labels over 63 bytes and mixed-script homograph risk.
URL Parser
WebParse a URL into scheme, host, port, path, query parameters and fragment, with each parameter shown raw and decoded. Runs entirely in your browser.
CIDR Calculator
WebTurn 192.168.1.0/24 into a network address, broadcast address, netmask, wildcard mask and usable host range. Runs in your browser.
User-Agent Parser
WebParse a user agent into browser, version, OS, device type and engine, and see which rules matched. Pattern matching only. Runs entirely in your browser.
HTTP Status Codes
WebLook up an HTTP status code for its meaning, 1xx–5xx class, typical uses and common traps. Runs entirely in your browser.
MIME Types
WebLook up a MIME type from an extension, or the default extension for a media type. Common types only. Runs entirely in your browser.