Qvantor logo QvantorInfrastructure, explained plainly
Security

Locking Down Your Domain Registrar Account the Right Way

A founder wrote to me last spring because his company email had stopped arriving. Not bouncing, just silent. He assumed the mail host had broken something.

A laptop on a desk showing a domain registrar control panel with DNS records beside a small hardware security key

A founder wrote to me last spring because his company email had stopped arriving. Not bouncing, just silent. He assumed the mail host had broken something. What had actually happened was that someone logged into his registrar account with a password reused from a 2019 forum breach, pointed the MX records at a server in another country, and spent four days quietly reading every invoice and password reset the company received.

That incident took eleven hours to unwind and cost more in lost invoices than his entire hosting bill for the year. The registrar account is the one login that almost nobody treats as critical, and it sits above every other account you own.

Why the registrar outranks the rest of your logins

Think about what a password reset actually proves. It proves that whoever clicked the link can read mail at an address on your domain. The domain's MX records decide where that mail goes, and the registrar decides who can edit the MX records. So the chain of trust for your bank, your cloud provider, your payroll system and your code host all terminate at one control panel that you probably last logged into when you renewed.

Hosting account compromise is noisy. Pages change, monitoring fires, customers complain. Registrar compromise is quiet, because an attacker who wants your mail does not need to break your website at all. They add a second MX record with a lower priority number than yours, collect what they want, and remove it. In the three cases I have looked at closely, the owner found out from a vendor asking why an invoice had been paid to a new bank account, not from any alert.

Transfer lock, registry lock, and the two people confuse

Registrars use overlapping names for different protections, which is why so many owners believe they are covered when they are not.

Transfer lock is the free one. It sets the status code clientTransferProhibited on the domain and blocks an outbound transfer to another registrar. Nearly every registrar turns this on by default now, and it is worth confirming rather than assuming. You can read the status yourself with a WHOIS lookup, or by running whois yourdomain.com from a terminal and looking at the Domain Status lines.

Here is the part that catches people out: a transfer lock does nothing about DNS edits. Someone inside your account can change nameservers, MX records and the registrant email while clientTransferProhibited sits there looking reassuring. The lock protects against the domain leaving. It does not protect against the domain being pointed somewhere else, which is the attack that actually happens.

Registry lock is the paid one, and it is a different mechanism. The lock is applied at the registry rather than the registrar, so changes require a manual out of band process, usually a phone call to a named contact with a passphrase, and it typically takes a day or two to lift. Verisign offers it for .com and .net, and resellers charge somewhere between 50 and 150 US dollars a year depending on how much hand holding they bundle in. For a domain that carries your billing email, that is cheap insurance. For a side project, it is overkill and the unlock delay will annoy you the first time you need a quick DNS change.

The counter-take: DNSSEC is not where you should start

Almost every hardening list puts DNSSEC near the top. I think that advice is misordered for small teams, and I say that as someone who has signed zones and enjoyed it.

DNSSEC stops an attacker from forging answers to DNS queries in transit. It does nothing at all once an attacker is inside your registrar panel, because then they are publishing signed records that genuinely belong to your zone. Every registrar hijack I have read about would have succeeded against a DNSSEC signed domain. Meanwhile, a botched key rollover or a registrar that drops your DS record during a transfer takes your whole domain off the internet, and resolvers will refuse your records rather than serve them unsigned. I have watched a two hour outage come out of exactly that.

Sign your zone eventually, especially if you run MTA-STS or DANE. Put it after the account level work, not before. The ordering that matches real risk looks like this: stop account takeover, stop unauthorised record edits, verify your contact address still belongs to you, then worry about forged answers on the wire.

A one hour audit you can run this week

Set a timer, open your registrar panel, and work through these in order. On a single domain this takes about forty minutes, and most of that is waiting for confirmation emails.

  1. Replace the password with something unique. If the registrar password exists in any other account, treat it as already known. A generated passphrase stored in a vault is fine here, and our notes on choosing a password manager for a small team cover how to share one without pasting it into chat.
  2. Turn on the strongest second factor the registrar supports, and check what that actually is. Several popular registrars still only offer SMS codes or an authenticator app. If yours supports WebAuthn, enrol two hardware security keys rather than one, because a lost key with no backup means a support ticket and an identity check.
  3. Delete SMS as a fallback if the panel lets you. A SIM swap on the account owner's phone number undoes every other control on this list, and the swap takes a motivated attacker one phone call to a carrier retail desk.
  4. Move the account email off the domain itself. If your registrar login is [email protected] and someone redirects your MX records, you have lost the ability to receive your own recovery mail. Use an address on a provider you do not control through this registrar, and protect that mailbox with the same care.
  5. Check the registrant, admin and technical contacts in WHOIS. Old agency addresses are the single most common finding. I have seen a domain where the admin contact was a freelancer who had stopped working with the company in 2021 and still received every ICANN verification notice.
  6. Confirm the domain status codes. You want clientTransferProhibited at minimum, and clientUpdateProhibited and clientDeleteProhibited if the registrar exposes them. Those last two are the ones that block record and nameserver edits, and they are the closest free equivalent to a registry lock.
  7. Turn on auto renew and verify the card on file has not expired. A .com that lapses enters a 30 day grace period, then a redemption period where the restore fee runs around 80 to 150 dollars, and after that anyone can register it. Expiry is a slower disaster than hijacking but the end state is identical. We walk through the recovery path in expired domain recovery steps.
  8. Write down who can authorise a change and tell the registrar's account team if you have one. Two named people with a shared passphrase is enough.

If you manage domains for clients, run this per account rather than once. The registrar account that gets compromised is always the one nobody remembered owning.

What registrar support can be talked into

Technical controls fail at the help desk. Every registrar has a process for an owner who has genuinely lost access, and that process is a social engineering target. The usual script is a caller claiming to be a new IT contractor, with the previous owner unreachable, in a hurry, offering a copy of a company registration document that took four minutes to fabricate.

What you can do about it is limited but not zero. Ask whether your registrar offers an account passphrase or a note on file requiring callback verification. Ask what documents their recovery process accepts. Some will tell you plainly. If the answer is that a copy of an invoice and the last four digits of the payment card is enough, you have learned something useful about where your domain actually lives, and moving to a registrar with a stricter process is a reasonable response.

One more habit worth the five minutes: subscribe to change notifications. Most registrars will email you on nameserver edits, contact changes and transfer requests, and those notices go to the account email you just moved off the domain. An attacker who edits records at two in the morning cannot easily suppress a message that was already sent. I have no numbers on how often that notification is what catches the problem, but in the one case I watched it was the only warning anybody got.

The rest of the account hygiene work sits in the security section, and the registrar audit pairs naturally with revoking access for people who have left.

Frequently asked questions

Does a transfer lock stop someone changing my DNS records?

No. clientTransferProhibited blocks a transfer to a different registrar and nothing else. Nameserver and record edits need clientUpdateProhibited, or a registry lock, or simply an account that an attacker cannot log into.

Is registry lock worth the yearly fee?

For a domain that carries company email, billing notices or customer logins, yes. For a hobby project, probably not, because every legitimate DNS change then needs a phone call and a wait of up to two business days.

Should my registrar and my DNS host be the same company?

Splitting them means two accounts to secure but it also means a registrar compromise alone does not hand over your zone, since the attacker would still need to repoint nameservers, which is a change your monitoring can catch. I keep them separate for anything that carries mail.

How do I tell if my MX records were tampered with?

Query them directly rather than trusting the panel, using dig yourdomain.com MX +short and comparing the output against what your mail provider documents. Look for an extra host with a lower priority number than your real one, which is how silent interception is usually set up.

ON
Obi Nwachukwu

Obi works on account security and explains phishing, passwords and access in plain terms.

More posts by Obi

More in Security

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto