Two of our guides end at the same doorstep. The one on what to do when a site rejects your alias concludes that the durable fix is an address at a domain you own, and our setup walkthrough assumes you have already bought one. The step in between, choosing and registering the domain itself, is the step almost nobody writes about. This is that guide.
It helps to state the domain's job plainly, because it shapes every decision that follows. A domain is a namespace you control. Addresses at someone else's domain are a tenancy: if the provider shuts down, changes its terms, or simply stops deserving your custom, every address you ever handed out goes with it. Addresses at your own domain survive all of that. You can change your forwarding service, your mailbox provider and even your registrar, and nothing you printed on a form or saved into a company's records has to change. That portability is the entire point of buying one.
It also means the purchase deserves a little more care than a casual website domain. An email domain is judged by spam filters, dictated over the phone, and trusted with account recovery. Each of those pulls the choice in a specific direction, so we will take them in turn.
The extension matters more than you would expect
The letters after the final dot, the top-level domain, are the least examined part of most purchases and the part strangers judge first. Mail filters have no opinion about your taste in names, but they do judge the TLD, and they have long memories about it.
The Spamhaus Project, which maintains blocklists used across the mail industry, publishes reputation statistics on top-level domains alongside periodic domain reputation reports. Its ranking of the most abused TLDs is worth understanding precisely because of what it measures: not the raw count of bad domains on an extension, but the ratio of domains its systems observe on that TLD to the domains it profiles as spamming or serving botnet and malware activity. A small, cheap extension where most registrations are throwaway spam domains can score far worse than a much larger extension whose bad domains are a small fraction of the whole. The names on the list shift from period to period, but the mechanism behind it is stable: Spamhaus notes that extensions offered at very low prices, or free, attract bulk registrations of disposable domains, and that you can often tell which registrar and TLD combination is on promotion simply by watching where known bad actors are registering in bulk.
The consequence for you is straightforward. Spam filters and signup validators use TLD reputation as one input, so a message from an address on a heavily abused extension starts its journey with a handicap, and some signup forms reject entire extensions outright. The bargain extension that costs a tenth of a .com is cheap because the people buying it in bulk do not intend to keep it.
The practical advice is dull and worth taking: for any address that must reliably arrive, stay on a mainstream extension. That means .com, an established generic such as .net or .org, or the country-code domain of a country you genuinely have a connection to. To be fair to the newer extensions, a clean domain on a mainstream TLD can still land in spam for other reasons, and plenty of mail from young TLDs is delivered without incident. But the extension is a reputation signal you choose exactly once and then carry on every message you send, and there is no reason to pick a burdened one to save a few pounds a year.
A domain with a past
Domains get registered, used, dropped and re-registered, and reputation systems track the domain, not the owner. A previously registered name inherits whatever its former holder earned: blocklist entries, a spam-filter history, associations with whatever the old site did. None of this is visible at the registrar. The checkout page for a domain that spent three years fronting a pharmacy spam operation looks identical to the checkout page for a name nobody has ever held.
So check before you buy, not after. Three checks cover most of it:
- Look it up on the public blocklists. Spamhaus's reputation checker at check.spamhaus.org reports whether a domain appears on its blocklists, and MXToolbox's blacklist check tests a name against a large set of DNS-based blocklists in one pass.
- Check the archived history. The Wayback Machine at web.archive.org keeps snapshots of what a domain served over the years. A record of parked pages or a defunct family business is fine; a record of pill adverts or link farms is a reason to walk away.
- Search for it. Put the bare domain into a search engine in quotes. Spam complaints, forum reports and old scam warnings all surface this way, and they are exactly the material a suspicious mail admin would find.
If a name you want fails these checks, the honest answer is to pick another name. Delisting from a blocklist is possible but slow, sometimes conditional, and never guaranteed, and a filter's private history of a domain is not something you can petition at all. A brand-new, never-registered name has no past to audit, which is a genuine argument for inventing a slightly odd name over buying a nice one on the aftermarket.
Say it aloud before you buy it
A website domain is mostly clicked and copied. An email domain is dictated: over the phone to your bank, across a counter, letter by letter to someone typing it into a form. Before buying, read the whole address aloud to another person and watch them write it down. If you have to spell it twice, explain a hyphen, or say the words "number four, not f-o-u-r", keep looking. Doubled letters where two words join, digits that could be words, and clever misspellings of real words all cost you every time the address is spoken. Shorter is better for the same reason, and because you will be typing this domain into cramped forms for years.
What actually matters in a registrar
For email, the registrar checklist is short, and price is the least of it. The first requirement is full control of DNS records: you must be able to create and edit MX records, which direct the domain's mail, and TXT records, which carry the SPF and DMARC entries that authentication depends on. Almost every mainstream registrar allows this, but some bundle domains with website builders that restrict DNS editing or route changes through support tickets. If a registrar's documentation cannot show you the screen where MX records are edited, buy elsewhere.
The second requirement is protection against losing the name. Turn on auto-renew and keep the payment card behind it current. Make sure renewal and expiry notices go to an address that is not on this domain, since a lapsing domain cannot receive its own warnings. Leave the registrar's transfer lock enabled, so the domain cannot be moved to another registrar without you deliberately unlocking it. And check the renewal price rather than the first-year promotion, because the renewal price is the one you will pay for a decade.
We are deliberately not recommending registrars by name. The capabilities above are the whole checklist, they are easy to confirm from a registrar's own documentation, and any registrar that meets them is adequate for mail.
The sensible defaults
If you want the short version, these defaults serve almost everyone.
| Decision | Sensible default | Why |
|---|---|---|
| Extension | .com or your country's ccTLD | Mainstream TLDs carry the least filtering baggage |
| New or previously owned | A never-registered name | Nothing inherited, nothing to audit |
| Name | Short, real words, no digits or hyphens | It will be dictated aloud for years |
| Registrar | Any with free MX and TXT editing | Mail setup is DNS editing, nothing more |
| Renewal | Auto-renew, notices to an off-domain address | A lapsed domain takes every address with it |
| Registration length | Multiple years where offered | Fewer chances for a renewal to fail quietly |
What the public record shows now
Registering a domain creates a public record, and much of the old advice about it is out of date. For years, a WHOIS lookup on a generic TLD routinely displayed the registrant's name, postal address, phone number and email. That position ended with the temporary rules ICANN adopted in 2018 to comply with European privacy law, and it is now formalised: under ICANN's Registration Data Policy, in effect for gTLD registries and registrars since 21 August 2025, personal data in public lookups is redacted wherever data protection law requires it, and registrars may redact it elsewhere too. Where a contact email is redacted, the lookup shows an anonymised forwarding address or a web form in its place, so there is still a way to reach you.
Redaction has limits worth knowing. Your registrar still collects and holds your real name, address and contact details, and can be required to disclose them under legal process. The public record still shows the registrar, the creation and expiry dates, and the name servers, so anyone can see which DNS or mail provider a domain points at. And the ICANN policy binds generic TLDs; country-code registries set their own publication rules, and some publish more than the gTLD baseline. If you are choosing a ccTLD, read that registry's policy before assuming redaction. After any purchase, look your own domain up and see exactly what is shown; paid WHOIS privacy add-ons overlap heavily with what the policy already requires on gTLDs, so it is worth checking what you would actually be buying.
The first day you own it
Resist the urge to start handing out addresses the moment payment clears. First make the domain actually deliver. Publish the MX and TXT records your forwarding service or mail provider specifies, give DNS time to propagate, then send test messages in both directions: from the new domain to an account you trust, and from an ordinary Gmail or Outlook account back to the new domain. Confirm the messages arrive, and arrive in the inbox rather than the spam folder. Our walkthrough on setting up email aliases in an hour covers the full sequence. Only once a test has landed should the domain go into anything permanent: a bank record, a recovery address, a business card.
The part nobody advertises
A domain is not bought, it is rented, and the rental can end. If the renewal fails, quietly or otherwise, every address on the domain stops working at once: the newsletter throwaways, the address your bank holds, and the recovery addresses protecting your other accounts. After the registrar's grace and redemption periods pass, the name returns to the open market, and whoever registers it next can receive mail sent to your old addresses, password resets included. This is the mirror image of portability. Owning the namespace means being responsible for it, permanently.
None of that is a reason to avoid a domain; it is a reason to treat renewal as seriously as a passport. Auto-renew with a current card, notices to an off-domain address and a multi-year registration reduce the risk to something small. It is also worth knowing how the service behind the domain fails: if you route the domain through a forwarding service, read what happens to your addresses if you stop paying before you depend on either. For a pile of low-stakes signups, aliases on a shared domain are simpler and carry none of this responsibility. The domain earns its keep at the point where your addresses need to outlive every provider you use, and for the addresses that matter for years, it is the only arrangement that does.