A fully qualified domain name (FQDN) is the complete, unambiguous name of a specific host — every label, from the host all the way up to the root of the DNS. For example, www.example.com is an FQDN: a host (www), a domain (example), a TLD (.com), and an implied trailing dot for the root. “Fully qualified” means it is absolute — nothing is assumed.
The phrase sounds intimidatingly technical, but the idea is simple: an FQDN is a domain name written out in full, with no shortcuts, so that it can only mean one exact location on the internet.
What is a fully qualified domain name?
To be “fully qualified” is to be complete and unambiguous. A name like mail is relative — mail on which network? But mail.example.com is absolute: it specifies the host, the domain it belongs to, the TLD that domain sits under, and (implicitly) the root above that. There is exactly one such name in the world, so it identifies one precise host.
Fully Qualified Domain Name — the complete name of a host, listing every label from the host up to the DNS root, e.g. www.example.com. (with the trailing dot for the root often implied).
The parts of an FQDN
Read right to left, an FQDN climbs the DNS hierarchy from the most general level to the most specific:
| Label | Level | Role |
|---|---|---|
. (implied) | Root | The unnamed top of the DNS. |
com | Top-level domain | The extension. |
example | Second-level domain | The registered name. |
www | Host / subdomain | The specific machine or service. |
The host label on the left (www, mail, api…) is what pins the name to a particular service — itself a subdomain of the registered domain.
FQDN vs hostname vs domain
These terms overlap, so it helps to line them up:
- Hostname — just the local label, e.g.
mail. Not unique on its own. - Domain name — the registered name, e.g.
example.com. - FQDN — the full path to a host, e.g.
mail.example.com. Globally unique and absolute.
A bare domain can be an FQDN too
example.com is itself a fully qualified name for the domain’s apex — it is complete up to the root. Adding a host label like www simply qualifies a more specific resource within that domain.
The trailing dot, explained
Strictly, a true FQDN ends with a dot: www.example.com.. That final dot stands for the root zone, the silent level above every TLD. It signals “this name is absolute — resolve it exactly as written.” In browsers and everyday writing the dot is dropped because it is implied, but in DNS zone files and some tools you will see it spelled out, and there it carries real meaning.
Where you'll meet FQDNs
FQDNs show up wherever software needs an exact, unambiguous target: TLS/SSL certificates (issued for specific FQDNs), DNS records and zone files, server and email configuration, network and firewall rules, and command-line tools like ping or dig. Anywhere “close enough” is not good enough, the fully qualified form is required.
Why the FQDN matters
The FQDN is the precise, machine-grade way to name a host. Understanding it clears up why a certificate might cover www.example.com but not example.com (different FQDNs), why a zone file ends names with a dot, and how a single registered domain can host many distinct services, each with its own fully qualified name. It is the bridge between the friendly domain you register and the exact host a computer connects to.
★ Key takeaways
- An FQDN is the complete, absolute name of a host, from the host up to the root.
- Example:
www.example.com.— host, domain, TLD, and the implied root dot. - A hostname is just the local label; the FQDN adds the full domain path.
- The trailing dot marks the root and makes the name absolute; it is usually implied.
Frequently asked questions
What does FQDN stand for?
FQDN stands for Fully Qualified Domain Name. It is the complete name of a specific host, listing every label from the host up to the root of the DNS — for example www.example.com. “Fully qualified” means nothing is left to be assumed.
What is an example of an FQDN?
mail.example.com is an FQDN: mail is the host, example is the second-level domain, and .com is the TLD — with an implied trailing dot for the root. example.com on its own is also an FQDN for the domain’s apex.
What is the difference between an FQDN and a hostname?
A hostname is just the local label of a machine, like mail. An FQDN is that hostname plus its full domain path, like mail.example.com, making it globally unique and unambiguous.
Why does an FQDN sometimes end with a dot?
The trailing dot (example.com.) represents the unnamed root of the DNS. A name ending in that dot is absolute — fully qualified. In everyday use the dot is implied and omitted, but in some technical contexts, like DNS zone files, it is written explicitly.
Is a URL an FQDN?
No, but a URL contains one. A URL adds a protocol and path around the host — https://www.example.com/page. The www.example.com part is the FQDN; the rest is URL structure. See domain name vs URL.
Why does my SSL certificate cover www but not the bare domain?
Because www.example.com and example.com are different FQDNs. A certificate is issued for specific fully qualified names, so one issued only for www.example.com will not validate the apex example.com unless that name is also listed. This is a common reason a secure-padlock error appears on just one form of the address.