From "I Paid $10" to "The Whole World Can Find My Site": Demystifying Domains, Registrars, and DNS¶

Many of us have purchased domain names on platforms like Cloudflare, GoDaddy, or Gandi. For a few bucks a year, it takes just a few clicks to secure one. But if you pause and think about it, several questions emerge: Who actually gets this money? If the registrar I used goes out of business, will my domain vanish? And when someone types my URL into their browser, how does their computer know where to connect?

Using a .com domain as an example, this post breaks down the entire lifecycle and mechanism from start to finish.

1. What You Buy Is a "Lease", Not Ownership¶

Let's clear up a common misconception first: Domain names cannot be bought permanently. The fee you pay every year secures the right to register that name for 12 months. As long as you renew on time, it remains yours; if you forget to renew, it will eventually be released after a grace period for anyone else to grab.

So rather than saying "I bought a domain," a more accurate phrasing is: "I registered this name with an authority and lease it annually."

2. Who Are You Actually Buying From?¶

Domain management operates across a four-layer chain:

ICANN (Global Overseer: sets rules, issues licenses)
└─ Registry (Manages a TLD; e.g., Verisign manages .com)
    └─ Registrar (Retailer; e.g., Cloudflare, GoDaddy)
        └─ Registrant (You)

• ICANN: The non-profit international organization that governs the overall domain system rules and issues licenses to registries and registrars.
• Registry: The "authoritative keeper" of a specific top-level domain (TLD). .com and .net are managed by the U.S. company Verisign, .tw by TWNIC, and .dev by Google. The authoritative records indicating who owns a name and where to direct it live inside the registry's database.
• Registrar: The user-facing retail channel. When you enter your info and swipe your credit card on Cloudflare, Cloudflare submits your registration into Verisign's database and handles future renewals for you.
• Registrant: That's you.

Take a .com domain on Cloudflare as an example. At around $10 a year, here is roughly where your money goes:

• The vast majority goes to Verisign: This is the wholesale fee set by the registry.
• $0.20 goes to ICANN: A fixed annual administrative fee collected per domain.
• Cloudflare makes almost no profit: They market domain registration "at cost" and monetize through other services. This is why Cloudflare is typically cheaper than other registrars.

To verify where your domain is registered, visit lookup.icann.org and enter your domain. The query results list the registrar, expiration date, and Name Servers (explained below). This public lookup system is historically known as WHOIS, now being replaced by RDAP.

3. If Your Registrar Goes Bankrupt, Will Your Domain Disappear?¶

The short answer is: The domain itself won't disappear, but your website might temporarily become unreachable. These two aspects must be evaluated separately.

1. Domain Ownership Is Protected by Protocol¶

• The master records aren't held by the registrar: The authoritative record sits with the Registry (Verisign), not the registrar. Even if your registrar goes bankrupt, Verisign's database still records that the domain belongs to you.
• Data Escrow Protection: ICANN mandates that every accredited registrar regularly back up customer data with an independent third-party escrow provider (Data Escrow). In the event a registrar goes under or loses its accreditation, ICANN follows a standardized procedure to bulk-transfer all domains under that registrar to another qualified registrar, where you can then claim management.

Historical Context: This safeguard wasn't built in a vacuum. In 2007, a registrar named RegisterFly mismanaged operations and collapsed, leaving thousands of customers at risk of losing their domains. ICANN drastically tightened regulations afterwards.

2. Why Websites Might Go Offline: Bundled DNS Services¶

The real vulnerability lies elsewhere. Many registrars provide DNS resolution services alongside domain sales—answering queries about which IP address corresponds to your domain. Cloudflare even mandates that domains registered through it use Cloudflare's Name Servers.

If Cloudflare were to experience a total outage, the DNS servers providing navigation directions would disappear too. Your domain ownership remains intact, but because nobody can resolve where it points, your site becomes unreachable until you transfer the domain or update the DNS settings elsewhere.

3. Practical Self-Protection Tips¶

• Use a long-term primary contact email: Transfer authorization, expiration warnings, and verification alerts are sent here. Update it immediately if you change jobs or providers.
• Know where to locate your Auth Code (Transfer Key): Domains cannot be transferred out during the first 60 days post-registration or transfer, but after that window, you can migrate to another registrar at any time.
• Enable auto-renewal and track expiration dates: In practice, the primary reason people lose domains isn't registrar failure—it's forgetting to renew.

4. How Does the World Find Your Website?¶

When someone types https://www.example.com into a browser, a step-by-step query process unfolds behind the scenes.

A quick detail: www isn't anything special—it's simply a subdomain prefix under the main domain, just like blog or api in blog.example.com or api.example.com, configured by you in your DNS records.

Asking Layer by Layer¶

1. Step 1: Ask a nearby DNS Resolver
   Your computer queries a DNS resolver, usually supplied by your ISP or a public provider like Google (8.8.8.8) or Cloudflare (1.1.1.1). If it cached the answer recently, it responds instantly; otherwise, it queries downstream on your behalf.
2. Step 2: Ask the Root Servers
   The resolver asks: "Who manages .com?" The Root Server responds: "Ask Verisign's .com TLD servers." Globally, there are 13 root server IP identities, though each is backed by massive distributed clusters worldwide.

3. Step 3: Ask the .com Registry
   The resolver then asks Verisign: "Who handles example.com?" Verisign checks its records and responds: "The Name Servers for this domain are xxx.ns.cloudflare.com. Go ask them."

   Core Value: The yearly fee you pay buys you this exact entry—a record in Verisign's database instructing the internet: "For this name, query these Name Servers."

4. Step 4: Ask the Domain's Authoritative Name Server
   The resolver finally asks Cloudflare: "What is the IP address for https://www.example.com?" Cloudflare checks the DNS records you set up in your dashboard and returns the IP, such as 203.0.113.10.

5. Step 5: Connect
   Once the browser receives the IP address, it connects directly to that host machine to fetch the page content.

This entire resolution lookup usually takes just a few dozen milliseconds, and answers are cached locally, so your computer doesn't repeat this full chain for every page request.

5. Are IP Addresses Provided by DNS Providers? Are They Permanent?¶

This is another common misconception. DNS providers do not supply IP addresses; they merely record and answer the mappings you configure.

Think of DNS as a phonebook. In your Cloudflare dashboard, you write "www → 203.0.113.10". Cloudflare faithfully mirrors this entry and answers anyone who inquires. Whether 203.0.113.10 belongs to you or changes over time depends on where your site is actually hosted:

• Renting Cloud Servers (AWS, GCP, Azure, etc.): IP addresses are assigned by your cloud provider. Assigning a static IP (like AWS Elastic IP) keeps it unchanged; dynamic IPs may shift if instances reboot or get recreated.
• Hosting at Home: IPs are assigned by your internet service provider (ISP). Residential networks usually get dynamic IPs that change on modem reboots or ISP adjustments. You can request a static IP from your ISP or use DDNS (Dynamic DNS) software to auto-update your DNS records when your IP changes.
• Enabling Cloudflare Proxy (The Orange Cloud): Visitors won't see your origin server's real IP address; they see Cloudflare's proxy IPs instead. Traffic routes through Cloudflare before reaching your server. These proxy IPs are maintained by Cloudflare directly.

Therefore, whether an IP address changes depends on the actual owner of the IP, not the DNS provider.

6. How Long Does It Take for DNS Changes to Propagate Worldwide?¶

This brings us to TTL (Time To Live).

Every DNS record includes a TTL value specifying how long recursive resolvers are allowed to cache the answer. If TTL is set to 300 seconds:

• Once a resolver looks up "www → 203.0.113.10", it reuses that cached response for the next 5 minutes without re-querying Cloudflare.
• After 5 minutes, the cache expires. The next visitor prompt forces the resolver to perform a fresh DNS lookup.
• If you changed your server IP during those 5 minutes, resolvers fetch the updated record once their local TTL expires.

Thus, DNS record modifications don't instantly flip across the entire globe simultaneously; propagation occurs progressively as individual resolver caches expire across different TTL countdowns.

Cloudflare's default TTL setting is "Auto" (~5 minutes), which is quite fast. When people mention "DNS changes take 24 to 48 hours," they usually refer to:

1. Legacy environments where TTLs were configured for long durations (e.g., days).
2. Changing Name Servers altogether. Updating Name Servers modifies records at the TLD Registry level (.com), where the registry TTL is often set to 48 hours.

Conclusion¶

To put it all together: The small fee you pay annually flows through your registrar to lease an authoritative registry record that says "For this name, query these Name Servers." Your Name Server then delivers the IP address you configured to internet visitors worldwide. The IP belongs to the actual server hosting your website, while TTL dictates how long that mapping is cached.

Understanding these distinct layers clarifies several common technical questions:

• No need to panic if a registrar fails: Your domain registration rights are safe at the registry level.
• If your site suddenly drops offline: Check if your host server's IP address shifted.
• If DNS changes aren't immediate: Simply wait out the TTL duration.
• Most importantly: Make sure auto-renewal is turned on!