A Domain Is Rented, Not Bought
Registering a domain gets you exclusive use for a defined term, typically one to ten years — not permanent ownership. Keep renewing and you can hold it indefinitely; miss once and it enters a reclamation process on a fixed schedule, where every stage costs more to reverse than the last.
Most people have no idea what that process looks like until a site goes dark one morning. The four standard stages are below. Pay particular attention to the third — that's where the expensive surprise lives.
| Stage | Rough duration | What happens |
|---|---|---|
| Registered | 1–10 years | Normal use; can renew and transfer registrar |
| Grace period | ~30 days after expiry | DNS has usually stopped, but you can still renew at the normal price |
| Redemption | ~30 more days | Requires a redemption fee, commonly USD 80–100 or more |
| Pending delete | ~5 days | No longer recoverable; then open for anyone to register |
Worth stressing: by the time a domain reaches the grace period, DNS resolution has usually already stopped. So if you discover the problem because the site broke, the clock has been running for a while. That's exactly why auto-renew and expiry monitoring have to be set up in advance rather than sorted out during an incident.
Three Things That Matter When Picking a TLD
The TLD is the last part of the domain (.com, .tw, .io…). These are what actually deserve weight:
- Target market and trust `.com` remains the most universally recognised and the one you never have to explain. If your customers are in Taiwan and local identity helps, `.tw` or `.com.tw` earns something. Conversely, obscure new gTLDs may be memorable but still carry lower trust with some users and corporate procurement processes — worth weighing in B2B contexts.
- The renewal price, not the first-year price Many new gTLDs attract registrations with a very low first year while the renewal is several times that, with no cap guaranteed. Look up the TLD's **standard renewal price** and multiply by the years you expect to hold it. That's the real cost.
- Eligibility and restrictions Some TLDs restrict who may register (a local registered entity, a particular industry), and some have unusual dispute or transfer rules. Obscure TLDs carry one rarely-mentioned risk too: if the registry operator struggles commercially, long-term stability is weaker than with mainstream choices.
What Actually Differs Between Registrars
Most of the difference between registrars isn't the first-year price — it's the terms you won't notice at signup but will meet every year afterwards. First is **renewal pricing**: promotional rates usually apply to year one only, reverting to standard price from year two, and the gap can be large.
Second is **whether WHOIS privacy is free**. Registration details are public by default — name, address, phone, email — and privacy protection substitutes proxy details for those fields. Some registrars include it free for the life of the domain; others bill annually, which adds up considerably over time.
Third are the **attached conditions**: whether transferring out costs anything, whether you're forced onto the registrar's own DNS, and whether a DNS management API exists. That last one matters especially to teams automating things — if you intend to issue SSL certificates automatically via ACME with DNS validation, whether your registrar exposes an API decides whether that's possible at all.
Transfer Locks: The Real Rules, and What's Changing
Moving a domain to another registrar runs into ICANN's transfer lock rules. Three situations currently trigger a 60-day hold: **within 60 days of initial registration**, **within 60 days of a previous transfer**, and **within 60 days of changing registrant contact details** (most registrars let you opt out of that last one in advance). Separately, the transfer authorisation code (EPP code) must be released to you within five calendar days.
Here's the part most articles get wrong: this rule **is changing, but hasn't landed**. ICANN's GNSO Council approved reform recommendations in late 2024 that would shorten the 60-day hold to 30 days (720 hours), but it still requires Board approval and registrar implementation, and no timeline is settled. So both "it's been abolished" and "it's a fixed 60 days" are currently imprecise — most registrars are still enforcing 60 days in practice, so confirm the current rule with yours before planning a transfer.
Three Protective Settings Worth Doing Now
These three take under ten minutes and prevent most of the disasters:
1. Enable registrar lock
This flags the domain `clientTransferProhibited`, blocking unauthorised transfers out. It's the most basic and most effective defence against domain hijacking. It's usually on by default, but it's worth confirming yourself, and you simply lift it when you genuinely want to transfer.
2. Auto-renew — and verify the payment method
Auto-renew alone isn't enough. The most common failure is an expired card nobody noticed: the renewal charge fails, and the domain lapses anyway. Put the card's expiry in your calendar too, and make sure renewal notices go to a mailbox somebody actually reads.
3. WHOIS privacy and a separate admin mailbox
Enable privacy so your contact details aren't publicly harvested. And critically, **don't use an address on this domain** as the registrar account contact — if the domain breaks and mail stops, you won't receive the password reset needed to fix it. Use a separate domain or a free mail service for that contact.
Three Things to Confirm Before Registering
Before you pay, establish these three:
- The standard renewal price Not the first-year promotion. Find the TLD's standard renewal figure and multiply by the years you expect to hold it.
- Transfer-out policy and how to get the auth code Whether transferring out costs anything, where the auth code lives in the control panel, and whether support has to be involved. This determines whether you can leave later.
- DNS management and API access Whether you can set arbitrary DNS records yourself, and whether an API exists. If you plan certificate automation or CDN integration, this is a hard requirement.
In Summary
Domains are cheap, but a domain is the root of the whole online presence — site, mail, and certificate validation all hang off it. The real cost and risk aren't in the registration fee; they're in renewal pricing, transfer flexibility, and whether you configured auto-renew and locking. Ten minutes on those three settings beats a redemption fee later by a wide margin.
If your domain already fronts a CDN or you issue certificates frequently, DNS API support directly determines whether that can be automated. Our SSL automation platform integrates with major DNS providers for exactly that — automatic validation and multi-node deployment.