A web address is not stored in one location. Its ownership record, nameserver delegation, technical settings, and website content can each sit with different providers and systems.
That distinction matters when you renew a name, move a site, update email routing, or troubleshoot a page that no longer loads. A registrar may manage the account you use to buy the name, but it doesn’t necessarily run the DNS service or host the website behind it.
This guide explains where each record lives, how the underlying systems interact, and what you can check yourself.
The Short Answer: A Name Exists Across Several Systems
When someone registers a name such as yourbusiness.com, four separate functions may be involved:
- The registry operates the official registration system for the relevant extension, such as .com, .org, or .de.
- The registrar sells and manages the registration service, including renewals, transfers, and customer account access.
- The DNS provider publishes the zone entries that tell internet resolvers where services such as websites and email are located.
- The web host stores files or runs the application that serves the website.
One provider can offer all four services, but they remain separate functions. A business can keep its registration with one company, use another for name resolution, and host its website elsewhere.
Three Records That Make a Web Address Work
The phrase “where is a domain stored?” combines several different records. Separating them makes the process easier to understand.
The registry-side registration record
The registry maintains the official record for names registered under its top-level domain. For example, Verisign operates the authoritative registry for .com and .net; it processes requests submitted through registrars rather than selling names directly to most end users.
This record covers the name’s status, term, sponsoring registrar, and other registry-level information. It is not the same as a website, a hosting account, or the full set of DNS entries used by the name.
Parent-zone delegation data
A registry’s public zone file has a narrower technical purpose. It can publish delegation information that directs resolvers to the nameservers responsible for a registered name.
A registration record and a TLD zone file are therefore not interchangeable. A name can remain registered while lacking an active delegation in the parent zone, for example, if nameservers have not been configured or a delegation is not published.
The root zone sits one level higher. It directs resolvers to the authoritative servers for top-level domains such as .com or .org; it does not list every name registered beneath those extensions.
Authoritative zone entries
After a resolver reaches the delegated nameservers, those systems return the configured zone entries. Common examples include:
- A and AAAA entries, which map a hostname to an IPv4 or IPv6 address
- MX entries, which identify mail-handling systems
- CNAME entries, which create an alias from one hostname to another
- TXT entries, often used for email authentication and service verification
The provider responsible for these entries may be the registrar, a hosting company, a specialist DNS platform, or an internal IT team.
Registrar and Registry: Different Responsibilities
Registrars and registries both work with registrations, but they serve different roles.
| Responsibility | Registrar | Registry |
| Customer relationship | Provides the account used to buy, renew, transfer, and manage a name | Does not usually sell directly to customers |
| Registration request | Validates and submits requests to the appropriate TLD operator | Processes eligible requests received from registrars |
| Account and billing | Manages customer-facing settings, renewal notices, and payment | Maintains the official record for its extension |
| Technical publication | May offer nameserver and zone-management services | Publishes parent-zone data for the TLD it operates |
For a .com name, the registrar is the company the customer works with. The registry operator maintains the official .com record. Those responsibilities remain distinct even when the registrar also provides hosting or DNS management.
From Purchase to Reachable Address
Buying a name does not automatically create a working website. Several actions must happen before a visitor can type an address into a browser and reach a service.
The registrar sends the request
The customer chooses an available name through a registrar. The registrar submits the request to the operator of the relevant extension. If the request meets the registry’s requirements, the registry records it.
The registrar then manages the customer-facing parts of the service, including the renewal period, transfer process, account access, and, depending on the provider, contact-data settings.
The parent zone identifies responsible nameservers
To make the name resolvable, the registry-side delegation must identify the nameservers responsible for it. A recursive resolver follows this delegation path from the DNS root to the relevant TLD and then to the designated nameservers.
This is why changing nameservers can take time to appear consistently. The registry must publish the delegation update, and resolvers may continue using cached information until its time-to-live expires.
The nameservers return service destinations
The designated nameservers answer requests with the zone entries configured for that name. For a website, the relevant host might resolve to an IP address through an A or AAAA record, or it might use a CNAME to point to another hostname.
For email, MX records identify the mail systems that should accept messages. You can change these settings without moving the registration to a different registrar.
Why Buying a Name Does Not Host a Site
Buying a domain, DNS management, and web hosting are often sold together, which can make them seem like one product. Operationally, they are different services.
- Registration reserves a name under a particular extension for a defined period.
- DNS hosting maintains the technical entries used to direct requests for that name.
- Web hosting stores site files or runs the software that generates pages for visitors.
A business can register company.com with one provider, manage its zone through another, and run the website on a third platform. The same applies to email: a provider can handle mail routing with no role in the website or the registration account.
A registered name can also exist without a website. Until you configure the appropriate zone entries and a hosting service, visitors may see an error, a placeholder page, or no response at all.
How to Check the Public Information
Different lookup methods answer different questions. Registration data does not show every DNS entry, and a DNS lookup does not reveal all information the registry or registrar holds.
Find the registrar and available registration details
The Registration Data Access Protocol, or RDAP, is the current standard for accessing available registration data for supported names. An RDAP result can identify the sponsoring registrar, status codes, important dates, and publicly available contact information.
Privacy laws and registry policies may limit what is displayed. That is expected and does not mean the registration record is missing.
Check nameservers and published zone entries
DNS lookup tools can show the nameservers currently published for a name and the records those servers return publicly. This is useful when investigating website routing, email delivery, verification records, or a recent provider migration.
A lookup can reveal published information, but it cannot expose every internal setting held in a provider account. It also cannot replace the registry’s official registration system.
Understand ICANN and IANA’s roles
ICANN coordinates policy and contractual arrangements for generic top-level domains, including agreements with many registries and accredited registrars. It does not register every name or operate every extension’s registration database.
IANA manages the root-zone management function and publishes the Root Zone Database. This resource identifies TLD delegations and the organisations responsible for them. It is not a directory of individual registrations.
Why a Registered Name Can Still Lead Nowhere
A name can be active in the registry while visitors cannot reach a functioning site. That usually points to a problem after registration.
Common causes include:
- No nameservers have been configured or published
- The nameservers do not return the expected zone entries
- A web record points to the wrong address
- The hosting account has been removed, suspended, or misconfigured
- Resolver caches still hold an older response after a change
The registration record confirms that the name remains reserved. It does not guarantee that a web server, mail service, or application is correctly configured behind it.
Conclusion
A web address is supported by several connected systems rather than one storage location. The registry keeps the official record for its extension, the registrar manages the customer service relationship, delegated nameservers answer technical lookups, and the web host delivers the site itself.
Knowing which provider controls each layer makes renewals, migrations, DNS changes, and troubleshooting more predictable. It also prevents a common mistake: assuming that buying a name automatically includes a live website.