Domain hijacking is one of the quietest ways to lose a business overnight. Attackers do not need to breach your servers. If they take control of your domain, they control where your website points, where your email goes, and who can get TLS certificates in your name. Your brand stays the same. Everything behind it now belongs to someone else.
The good news: most hijacks rely on weak account security and forgotten settings, not advanced exploits. This guide explains how domain hijacking works, the most common attack paths, and a practical checklist to lock your domain down.
What Domain Hijacking Is and Why It Hurts
ICANN’s Security and Stability Advisory Committee defines domain hijacking as the wrongful taking of control of a domain name from its rightful holder. In practice, the term covers several attacks that end in the same place: someone else decides what your domain does.
What attackers can do with your domain
- Steal email: change MX records and receive password resets, invoices and customer messages.
- Run phishing: host fake login pages on your real domain, which users and filters trust.
- Intercept traffic: point users to servers they control and read what passes through.
- Damage your brand: deface the site or hold the domain for ransom.
The four main forms
| Type | What happens |
|---|---|
| Registrar account takeover | Attacker logs in to your registrar and transfers or edits the domain |
| DNS hijacking | Attacker changes nameservers or records at your DNS provider |
| Expiry capture | The domain lapses and someone else registers it |
| Subdomain takeover | An old DNS record points to a deleted service the attacker can claim |
Your domain is not just a website address.
It is the root of trust for your email, logins and certificates.
How Attackers Take Over Domains
Stolen registrar credentials
The most common path. A phishing email, a reused password or a missing MFA setting gives the attacker your registrar login. From there, they can unlock the domain, get the transfer code, or simply change the nameservers.
Social engineering the support desk
Some attackers skip your password and call the registrar instead. They pose as the owner, claim they lost access, and ask support to reset the account. ICANN’s SSAC found that weak identity checks in registrar processes, and publicly listed contact details, have helped attackers impersonate registrants.
Expired domains
No hacking needed. An expired card, a renewal notice sent to an old inbox, and the domain drops. Anyone can register it and receive your email traffic.
Dangling DNS
A subdomain still points to a cloud bucket, app or CDN that you deleted. If the attacker can claim that resource name, they serve content on your subdomain without touching your main domain at all.
Domain Hijacking Prevention Checklist
1. Lock down the registrar account
- Use a unique, long password stored in a password manager.
- Turn on MFA, ideally a passkey or hardware key rather than SMS.
- Use a recovery email on a different domain. If your account email lives on the domain you lose, you lose the recovery path too.
- Limit who has access, and remove former staff and agencies.
2. Use every lock available
A registrar lock sets status codes such as clientTransferProhibited and clientUpdateProhibited. These block transfers and changes until you unlock the domain. SSAC found that consistent use of registrar locks, unique transfer codes and transfer notices can prevent many hijacks. For high-value domains, ask about a registry lock. It adds a manual, out-of-band check at the registry level, so even a compromised registrar account cannot change the domain alone.
3. Never let it expire
Turn on auto-renew, keep a valid payment method, and renew for several years at a time. Put the expiry date in a shared calendar, not one person’s inbox.
4. Protect and monitor DNS
- Secure your DNS provider account the same way as your registrar.
- Enable DNSSEC where your registrar and DNS host support it.
- Set alerts for nameserver and record changes.
- Watch Certificate Transparency logs for certificates you did not request.
- Delete DNS records the moment you retire the service behind them.
These steps mirror CISA’s Emergency Directive 19-01, issued after a wave of DNS tampering against US agencies. It told agencies to audit DNS records, change DNS account passwords, add MFA and monitor Certificate Transparency logs.
5. Keep contact details private and current
Use WHOIS privacy so attackers cannot harvest your contact details for phishing or impersonation. Keep the real contact data at your registrar accurate, so renewal and transfer notices reach you.
Strong identity controls protect your domain too. Read our Zero Trust access management guide
What to Do If Your Domain Is Hijacked
- Call your registrar’s emergency or abuse line right away and ask them to freeze the domain.
- Collect proof of ownership: invoices, account history and past WHOIS records.
- Warn users and partners that email and links from the domain may not be safe.
- Reset every password that could have been reset through email on that domain.
- Escalate through ICANN’s transfer dispute process if the domain moved to another registrar.
SECITHUB Take
The most dangerous setup is also one of the most common: a registrar account protected by a password and an email address on the same domain it manages. Lose one, and you can lose both. Fixing this takes ten minutes. Move the recovery email to another domain, add phishing-resistant MFA, check that auto-renew is on, and confirm the transfer lock is active. Few security tasks give this much protection for so little effort.
Attackers do not need your servers.
They just need your registrar login.
Have you checked your registrar security settings lately?
Share your checklist at r/secithubcommunity

Domain hijacking is the wrongful taking of control of a domain name from its rightful owner. Attackers usually do it by taking over the registrar account, changing DNS settings, registering an expired domain or claiming a forgotten subdomain.
The most common methods are stolen registrar passwords, social engineering of registrar support, domains that expire without renewal, and dangling DNS records that point to deleted cloud resources.
A registrar lock sets domain status codes such as clientTransferProhibited and clientUpdateProhibited. These block transfers and changes until the owner removes the lock in the registrar account.
A registrar lock is controlled from your registrar account. A registry lock adds a manual verification step at the registry level, so changes need out-of-band approval even if the registrar account is compromised.
DNSSEC helps prevent forged DNS answers, but it does not stop an attacker who already controls your registrar or DNS account. Use it together with strong account security, locks and change monitoring.
Contact your registrar’s emergency or abuse line immediately, gather proof of ownership, warn users, reset passwords tied to email on that domain, and use ICANN’s transfer dispute process if the domain moved to another registrar.
Sources
SAC 007: Domain Name Hijacking: Incidents, Threats, Risks and Remediation – ICANN SSAC
Emergency Directive 19-01: Mitigate DNS Infrastructure Tampering – CISA


