Fully qualified domain name (FQDN): definition, rules, structure, and practical uses

To put it simply: "example.com" is a domain, but "www.example.com" is an FQDN when it points to a specific host. This guide covers what an FQDN is, how to recognize its structure, where FQDNs matter in practice, and how to find yours.

What is a fully qualified domain name?

A fully qualified domain name is a domain name that specifies its exact location in the DNS tree hierarchy by including all domain levels in a single, complete address: the hostname, the domain name, and the top-level domain (TLD). Technically, a true FQDN ends with a trailing dot (www.example.com.) that represents the DNS root, but browsers and most tools assume the root and do not require you to include it.

FQDNs identify a specific host or service, not just a registered domain.

"example.com" without a hostname is a partially qualified domain name (PQDN), it identifies the domain but not the exact host. A partially qualified domain name (PQDN), is a name whose interpretation depends on local DNS context.

FQDN structure: the rules

FQDNs follow a defined set of technical constraints that are set by DNS standards:

The table below shows valid and invalid FQDN examples:

Common FQDN uses in practice

FQDNs appear across several critical infrastructure contexts. Understanding where they are used helps when configuring domains, SSL certificates, or server environments.

DNS resolution

When you type an FQDN into a browser, the DNS resolver uses the full label path to find the IP address of the specific host. The FQDN is the input; the IP address is the output. DNS resolution works by querying a hierarchy of servers, starting from the root zone, then the top-level domain, then the second-level domain, to locate the authoritative DNS server for the hostname in question.

SSL/TLS certificates

SSL certificates are issued for a specific FQDN (or wildcard FQDN like *.example.com). A certificate issued for www.example.com does not automatically cover mail.example.com, each FQDN is a distinct host in DNS terms. This matters when configuring HTTPS across multiple subdomains: each one requires its own SSL certificate, or a wildcard or Subject Alternative Name (SAN) certificate that explicitly lists all the FQDNs to encrypt.

Server and network configuration

FQDNs appear in server configuration files, email server setup (MX records), VPN configurations, and internal IT systems where a specific host must be uniquely addressed. When configuring a web server or a mail transfer agent, you typically reference the server by its FQDN rather than just a hostname, so the server can be located from anywhere in the DNS hierarchy.

Email delivery

The sending mail server's FQDN is part of the SMTP handshake and is checked against DNS PTR (pointer) records during email delivery. A misconfigured or missing FQDN in PTR records can cause emails to be flagged as spam or rejected outright by receiving mail servers.

Before configuring any of the above, compare domain registration and renewal prices across registrars, TLD-list tracks prices across 100+ registrars so you can choose the right registrar for your DNS setup.

FQDN vs. PQDN vs. hostname vs. URL

These four terms are often confused because they all describe parts of the same address structure. Here is how they differ:

The key distinction between an FQDN and a URL: an FQDN identifies a host in DNS. A URL is the full address used to retrieve a specific resource over a protocol (HTTP, HTTPS, FTP). The FQDN is one component of the URL. The protocol (https://) and the path (/inbox) are URL components, not part of the FQDN itself.

A hostname alone ("mail") identifies the device within a local network but has no meaning outside of it. An FQDN gives that hostname its globally unique address by appending all parent domain levels.

How to find your FQDN

The method for finding your FQDN depends on your operating system. Below are the steps for the three most common environments.

Windows

Open Command Prompt and run:

hostname

To get the full FQDN, run:

ipconfig /all

Look for "Host Name" and "Primary DNS Suffix." The FQDN is hostname.primarydnssuffix combined. For example, if the hostname is SERVER01 and the primary DNS suffix is corp.example.com, the FQDN is SERVER01.corp.example.com.

macOS and Linux

Open Terminal and run:

hostname -f

The -f flag returns the FQDN. If the command returns only a hostname without a domain suffix, DNS may not be fully configured on the machine and the local hostname resolver may need to be updated.

Hosting control panels

Most web hosts display the server FQDN in the hosting dashboard under server information or DNS settings. For a shared hosting account, the FQDN typically points to the shared server, not your custom domain. Your registered domain is separate from the server's FQDN.

After verifying your FQDN, use TLD-list to find the right domain extension for your project and compare prices before you register.

Frequently Asked Questions

About the Author:

TLD-list

Editor team

Small crew of builders who believe a great idea should not be held back by a bad domain deal. We know this space inside out, from obscure new extensions to the registrar tricks that quietly inflate your renewal. We put that knowledge to work so you can spend less time worrying about domains and more time building the thing that matters.