
Domain hijacking — also called domain theft — is the unauthorised transfer of a domain name to a different registrar or owner without the legitimate owner's consent. The attacker gains control of your domain, and with it, your website, email, and online identity.
Unlike server breaches, which attack your infrastructure, domain hijacking attacks the naming layer above your infrastructure. Even if your servers are perfectly secure, a hijacked domain renders them unreachable — or worse, redirects your traffic to a malicious site while your brand takes the blame.
The most common vector. Attackers gain access to your domain registrar account (GoDaddy, Namecheap, Cloudflare, etc.) through phishing emails targeting domain administrators, credential stuffing using leaked passwords from other breaches, or social engineering registrar support staff.
Once inside, they change the registrant contact and initiate a transfer to a registrar they control.
Attackers impersonate the domain owner and convince registrar support to override security controls or release a transfer. This is less common now that registrars have improved identity verification, but it still occurs.
If you fail to renew a domain on time, it enters a redemption period and eventually becomes available for public registration. Competitors or squatters register it immediately. This is technically legal but devastating.
A related but distinct attack — rather than transferring the domain, attackers compromise your DNS provider credentials and change your DNS records to redirect traffic. Your WHOIS still shows you as the owner, but users are sent elsewhere.
A hijacked domain can cause:
Recovery can take days to weeks, even with proof of ownership, because domain transfers involve multiple parties and compliance periods.
The fastest automated detection method. Your monitoring tool polls the WHOIS record for your domain on a schedule and alerts you when the registrant name, registrant email, registrar name, or nameservers change unexpectedly.
Legitimate WHOIS changes are rare. If your monitoring alerts you that the registrant contact changed, treat it as a confirmed incident until proven otherwise.
Domain Monitor includes WHOIS monitoring with alerting for registrar changes, making domain hijacking detectable within minutes rather than hours or days.
Monitor your domain DNS records for unexpected changes:
If your A record changes to an IP you do not recognise, or your NS records point to nameservers you did not configure, something has gone wrong. This can indicate nameserver hijacking or registrar compromise.
Certificate transparency logs record every SSL certificate issued for a domain. Tools like crt.sh allow you to search these logs. Unexpected certificates issued to entities you do not recognise can indicate that an attacker has gained control of your domain.
Certificate Transparency monitoring is available through several security tools and provides early warning of fraudulent certificate issuance.
Monitor your domain expiry date and alert well in advance of renewal. A 60-day warning followed by a 30-day and a 14-day alert gives you multiple opportunities to renew before the domain enters a vulnerable state.
Many domain hijacking incidents are opportunistic — attackers monitoring for expiring domains and registering them immediately upon expiry. Robust expiry monitoring eliminates this risk. See monitoring SSL certificate expiry for a similar approach applied to certificates.
If your domain has been hijacked and DNS now resolves to attacker infrastructure, your uptime monitoring will detect this — either as a connection failure if the attacker has not set up any response, or as unexpected content if you use content verification.
An uptime monitor checking for a specific string in your homepage response will alert immediately when that string disappears. This is the final safety net.
Every major registrar offers a domain lock feature, also called transfer lock or registrar lock. When enabled, outbound transfers are blocked until the lock is explicitly disabled. Disabling the lock typically requires 2FA or identity verification.
Enable this for all domains. It is the single most effective prevention measure.
Enable two-factor authentication on your domain registrar account. Use an authenticator app rather than SMS — SIM-swapping attacks can bypass SMS 2FA.
The email address associated with your domain registrar account is a high-value target. Use a dedicated email address not connected to your main domain for registrar communications. This prevents attackers who compromise your domain email from also accessing your registrar account.
For critical domains, consider registry lock — a higher-security lock applied at the registry level rather than the registrar level. Registry locks require out-of-band verification, often a phone call, to release. This is typically a paid enterprise-level service.
DNSSEC cryptographically signs your DNS records, making it impossible for attackers to serve forged DNS responses. While it does not prevent domain transfer, it significantly raises the bar for DNS manipulation attacks.
Regularly review who has access to your registrar account, what API keys or tokens are active, and whether contact details are current and point to controlled inboxes.
If you discover your domain has been hijacked, act immediately:
Recovery is possible but takes time. Prevention through monitoring and registrar security is far preferable.
The strongest protection combines:
| Layer | What It Catches |
|---|---|
| WHOIS monitoring | Registrant changes, registrar changes |
| DNS monitoring | A, MX, NS record changes |
| Domain expiry alerts | Lapsing registration |
| SSL cert transparency | Fraudulent certificate issuance |
| Uptime monitoring | Traffic redirection, DNS resolution failure |
No single layer catches everything. Together they give you detection within minutes of any domain-level attack. See the website monitoring checklist for developers for a complete approach to monitoring across all layers.
WHOIS and DNS change monitoring catches domain hijacking within minutes. Set up domain monitoring at Domain Monitor.
Generative AI creates new content — text, images, code, and more. This guide explains how it works, what tools are available, and where it's genuinely useful versus overhyped.
Read moreCursor AI is an AI-powered code editor built on VS Code. Learn what it does, how it works, and whether it's the right tool for your development workflow.
Read moreClaude Opus is Anthropic's most capable AI model, built for complex reasoning and demanding tasks. Learn what it does, how it compares, and when to use it.
Read moreLooking to monitor your website and domains? Join our platform and start today.