Registrant
The person or organisation holding the registration rights.
controls the domain
Behind the address bar
How do domains work?
A domain works through delegation and DNS. When you enter a name, a resolver follows the DNS hierarchy until it reaches the authoritative records that say where the requested service lives.
Try
Live availability across hundreds of extensions. Free, no signup.
The core concept
A lookup follows delegated authority
The answer is not stored in one giant directory. Each layer points the resolver toward the next authority.
ResolverAsks and caches
›
RootPoints to TLD
›
.comPoints to domain
›
AuthoritativeReturns records
Cached answers can skip some steps until their time-to-live expires, which is why repeat visits are normally faster.
The essentials
Registrar
The company through which the registrant manages the registration.
account · renewal · transfer
Registry
The operator maintaining registrations for one top-level domain.
one registry per TLD
DNS operator
The provider serving authoritative records for the domain.
nameservers · records
What happens after you press Enter
A typical web visit combines name resolution with a separate connection to the resulting server.
Browser checks nearby caches
The browser and operating system first look for a still-valid cached answer.
Resolver finds the authority
If needed, the recursive resolver follows root and TLD referrals.
Authoritative DNS answers
The domain's nameserver returns the requested record and its cache lifetime.
Browser connects
The browser connects to the resulting destination, negotiates HTTPS and requests the page.
Control is divided across layers
Understanding the boundary makes provider changes and outages much easier to diagnose.
| Layer | Controls | A failure looks like |
|---|---|---|
| Registration | Who holds the name and its delegation | Expired, locked or wrong nameservers |
| Authoritative DNS | Records for web, email and verification | Name does not resolve or points elsewhere |
| Hosting | Website files and application responses | DNS works but the site errors or times out |
| Browser/HTTPS | Connection and certificate validation | Certificate or protocol warning |
A clean domain setup
- Keep registrar and DNS-provider accounts protected with multi-factor authentication.
- Know which provider is authoritative before editing DNS records.
- Lower TTL before a planned move, not after changing the destination.
- Keep website and mail records documented before replacing nameservers.
- Verify HTTPS after any DNS or hosting migration.
- Test both the bare domain and the www hostname.
Common questions
Does DNS contact the root servers on every visit?
No. Recursive resolvers cache referrals and answers for their published TTL, so many lookups are answered without repeating every step.
Why can a DNS change appear at different times?
Resolvers keep old answers until their TTL expires. Different users may therefore see different valid cached answers during a planned change.
Can the registrar and DNS provider be different?
Yes. The registrar manages the registration, while the delegated nameservers can belong to a separate DNS provider.
Does registering a domain create a website?
No. Registration reserves the name. You must also configure DNS and connect a website or application host.
Keep learning
The next concepts to understand
Next step
Inspect a real domain
Search a name, then compare its registry, DNS and live-site signals in one place.