What is a fully qualified domain name + real-life examples

Key takeaways: 

• Fully qualified domain names (FQDNs) offer convenience and organizational benefits. 
• FQDNs are complete DNS addresses that identify a specific host, service, or resource on a network.
• FQDNs help clearly identify resources on the internet without confusion. 

Domain names help people find websites without needing to remember long strings of numbers. But some online addresses need to be more specific than a regular domain name. That’s where a fully qualified domain name, or FQDN, comes in.

An FQDN gives the complete path to a specific server, host, or service within the Domain Name System (DNS). It tells browsers, email servers, and other systems exactly where to go, whether they’re loading a website, delivering an email, or connecting to another network resource.

In this guide, you’ll learn what an FQDN is, what it means, how it works, how it differs from a URL and a domain name, and how to find one on your device or server.

What is a fully qualified domain name (FQDN)?

A fully qualified domain name (FQDN), also known as an absolute domain name, is the complete and specific address of a server, host, or online resource. It includes every part needed to identify an exact location within the Domain Name System.

Think of it like a full mailing address. A street name alone may point you in the right direction, but it doesn’t tell you the exact house, city, state, or zip code. An FQDN works the same way. It gives the full address, so the system doesn’t need extra information to find the right destination.

For example, in the FQDN “mail.example.com,” “mail” identifies the mail server, “example” is the domain name, and “.com” is the top-level domain (TLD). Together, these parts create a complete path to a specific mail server under the example.com domain. 

What are the elements of an FQDN? 

Every FQDN is made of domain labels arranged in a hierarchical structure. Each label is separated by a dot, and each part helps the Domain Name System understand where a host or service belongs.

A complete FQDN may include: 

• Hostname
• Subdomain
• Second-level domain
• Top-level domain
• Trailing dot

Using “www.blog.example.com.” as an example, each part points to a different level in the DNS hierarchy.

Top-level domain

The top-level domain (TLD) is the last visible part of a domain name before the optional trailing dot. It sits at the highest level of the DNS hierarchy.

For example, in “www.blog.example.com,” “.com” is the TLD. Other common TLDs include:

• .org
• .net
• .shop

TLDs help categorize domain names by purpose, location, or type. For example, .com is widely used by businesses, while .org is commonly associated with organizations.

Second-level domain 

The second-level domain sits directly before the TLD. It’s usually the most recognizable part of the domain because it often contains the business, brand, organization, or website name.

In “www.blog.example.com,” “example” is the second-level domain. This is the part many people think of first when they talk about a website’s domain name.

Subdomain 

A subdomain comes before the second-level domain. It helps organize different areas, services, or sections under the same main domain. In “www.blog.example.com,” “blog” is the subdomain.

A business might use “blog.example.com” for articles, “shop.example.com” for an online store, or “support.example.com” for customer help.

Subdomains make it easier to separate content or services while keeping them connected to the same main domain. 

Hostname 

Hostnames typically appear in the leftmost part of the FQDN. You’ll see it after the http:// or https:// of a web address. It identifies the specific server, device, or remote host that provides a service on a network.

For example: 

• www for web servers  
• mail for mail servers  
• ftp for file transfer servers

The hostname helps route requests to the right place, especially when a single domain hosts multiple services. To better understand how hostnames compare with domains, read our guide to hostname vs. domain name.

Trailing dot

The trailing dot, also called a trailing period, appears at the end of a fully qualified domain name. For example, the complete form of “www.example.com” is technically “www.example.com.”

The dot represents the DNS root, which sits at the top of the Domain Name System. In everyday browsing, web browsers usually hide or ignore the trailing dot because “www.example.com” is easier for people to read.

However, the trailing dot still matters in technical settings, especially in DNS zone files. It tells the DNS that the name is complete and should not be treated as relative to another domain.

How an FQDN works

An FQDN works by giving the Domain Name System a complete name to resolve. When you type a website address into a browser, the browser needs to find the server connected to that name. It does this through DNS queries.

First, your browser or device checks whether it already has the answer saved in its cache. If not, it sends a query to a DNS server. The DNS server then looks up DNS records to find the IP address associated with that FQDN.

Let’s take this as an example: When you enter “www.example.com,” the FQDN serves as the complete name that DNS can use to find the correct web server. Once DNS finds the matching IP address, your browser can load the website.

This same process helps other services work, too. Mail servers use FQDNs to route messages to the right destination. If an FQDN is missing, incomplete, or misused in DNS records, it can cause problems such as connection errors when accessing websites or email delivery failures.

In simple terms, an FQDN gives DNS the full name it needs to send users, browsers, and services to the right place.

Real-world fully qualified domain name examples

FQDNs appear across many network resources, not just public websites. They can point to web servers, mail servers, file transfer protocol servers, database servers, cloud services, and internal systems within an organization.

Here are some more examples to illustrate their structure and diversity:   

Server type	FQDN example	Subdomain (s)	Second-level domain	Top-level domain (TLD)	Purpose
Web server	www.example.com	www	example	.com	Points to the main web server of the example.com domain.
Mail server	mail.company.org	mail	company	.org	Accesses the email server of company.org.
FTP server	ftp.archive.net	ftp	archive	.net	Used for file transfers via FTP for archive.net.
Database server	db1.internal.example.com	db1, internal	example	.com	Accesses a specific database server within the internal network.
API server	api.service.example.co.uk	api, service	example	.co.uk	Points to an API server for service.example.co.uk.
Cloud service	cloud-storage.enterprise.com	cloud-storage	enterprise	.com	Leads to a cloud storage service for enterprise.com.
Educational institution	student.portal.university.edu	student, portal	university	.edu	Represents a student portal of university.edu.
Government website	services.department.gov.us	services	department	.gov.us	Points to a specific service of a U.S. government department.

Depending on the operating system or network setup, FQDNs can also identify computers, printers, servers, and other devices within a private environment.

FQDN vs. URL vs. domain

The terms fully qualified domain name, URL, and domain are related, but they don’t mean the same thing. Here’s the difference:

• FQDN: An FQDN is the complete domain name that identifies a specific host, server, or service in DNS. It may include a hostname, subdomain, second-level domain, top-level domain, and trailing dot. For example, “mail.example.com” points to a specific mail server.
• Domain: The main name registered for a website or online property. For example, “example.com” is a domain. It can support many FQDNs, such as “www.example.com,” “mail.example.com,” or “shop.example.com.”
• URL: A URL is the full web address used to access a specific page or resource. It can include the protocol, FQDN or domain, path, and query parameters. For example, “https://www.example.com/products?color=blue” is a URL.

In simple terms: a domain is the main registered name, an FQDN identifies a specific host or service, and a URL tells a browser how to reach a specific page or resource.

How FQDN is different from PQDN

A partially qualified domain name (PQDN) lacks the full hierarchy of labels needed to identify a resource without additional context. It’s just a shortened version of a domain name.

For example, “example” or “mail” could work as a PQDN inside a private network where the system already knows which domain to add. But on the wider internet, those shortened names are too vague.

FQDNs include the hostname, domain name, and TLD, such as “www.example.com.” A PQDN may leave out one or more of those parts. That’s why an FQDN appears more often in public DNS records, server settings, and website configurations where the exact destination matters.

Technical insights: FQDN vs. PQDN 

FQDNs provide globally unambiguous names for Internet resources. They help ensure each address points to a specific location, even when many services exist under the same domain.

PQDNs can still be useful in local networks, internal systems, or controlled environments. However, they depend on context. Outside those environments, they can cause confusion because they don’t provide the complete path needed to identify the correct resource.

What are the benefits of using FQDNs? 

FQDNs make it easier to access resources without relying on numerical IP addresses. Instead of asking users or systems to remember numbers, FQDNs provide clear, readable names for websites, servers, email systems, and other web services.

They also help organize services under one domain. A business can use “www.example.com” for its website, “mail.example.com” for email, and “shop.example.com” for its online store. This makes accessing domain services easier because each service has a clear address.

Another benefit is stability. IP addresses can change when you move servers, update hosting, or adjust your infrastructure. An FQDN can remain the same while DNS records are updated behind the scenes to point to the new IP address. This helps users and systems keep reaching the right service with less disruption.

You can learn more about how domains can point to different destinations by reading our article about domain pointing.

To get SSL certificates 

FQDNs are used in Secure Sockets Layer (SSL) certificates. An SSL certificate helps encrypt data between a user’s browser and a website. Certificate authorities (CAs) issue these certificates, which secure and encrypt data between a user and a website, to websites with a valid FQDN.

This matters because SSL certificates bind a domain to its server name. If the FQDN in the certificate does not match the FQDN users visit, browsers may show a security warning. A certificate issued for “www.example.com” may not automatically cover “shop.example.com” unless the certificate is configured to include it.

To optimize your website 

A clear FQDN can make your website and services easier to manage, remember, and share. It helps users understand where they are going and helps teams separate different services under one domain.

FQDNs can also support a cleaner technical organization. When each service has a specific name, teams can manage DNS records, SSL certificates, hosting settings, and service connections more clearly.

How to find a fully qualified domain name

FQDNs aren’t limited to websites only. Your device also has its own FQDN.

To locate them, here’s how:

For Windows users  

1. On the Start menu, search and click View your PC name. 
2. In the Related links row, click Advanced system settings.

You’ll see FQDN in the Full Computer Name field. 

For macOS users 

If you want to see if your Mac is assigned to a specific DNS search domain via your router or network:

1. Open the Apple menu > System Settings.
2. Click Network in the sidebar.
3. Click on your active connection (like Wi-Fi or Ethernet), then click Details…
4. Click on the DNS tab.
5. Under Search Domains, you will see the domain suffix that attaches to your hostname to create your FQDN on that network.

For Linux users 

1. Press CTRL + ALT + T to open the Terminal app. 
2. Enter hostname –fqdn

Disclaimer: Actual process may vary depending on your OS version, permissions and system settings.

Frequently asked questions 

The clearer the address, the easier the path

A fully qualified domain name gives browsers, servers, and network systems the complete address they need to find the right destination. It removes guesswork behind the scenes.

A well-structured domain setup can help organize your website, support secure connections, separate key services, and create a smoother experience as your online presence grows.

Start with the domain that holds it all together. With Network Solutions, you can search for the right domain name, manage DNS settings, connect to a professional email, secure your site with SSL, and build your business online from one place.

Find the domain name that points your business in the right direction. Use our domain name search tool to find the perfect domain name for your brand!