DNS Hijacking, Domain Spoofing and Lookalikes: What Is the Difference?
Published 2026-11-14 · Reviewed 2026-11-14 · 6 min read · By the Ingenious AI team
Is someone impersonating your domain right now?
Run the free DomainGuard scan: lookalike registrations, MX-armed variants, certificate-transparency and CAA checks for your domain, in one report.
Run my free DomainGuard scanThe short answer
DNS hijacking takes control of your real domain's settings — through a registrar or DNS account — and repoints your actual traffic. Domain spoofing forges your exact domain in email without controlling anything, exploiting receivers that do not enforce authentication. Lookalikes avoid your domain entirely and imitate it with a different name. The three are confused constantly because the headlines look alike, but they have different mechanics, different evidence, and different fixes: account security and locks for hijacking, DMARC enforcement for spoofing, monitoring and takedown for lookalikes.
Hijacking: the attacker holds your actual name
In a hijack, the domain your customers type is the domain that betrays them. The attacker gains control at the registrar or DNS layer — compromised account credentials, a social-engineered registrar support call, an expired domain re-registered — and changes where your name points: the website's A records, the mail's MX records, sometimes the nameservers wholesale. Everything downstream of DNS inherits the compromise, including the ability to pass domain-validation and receive certificates for your real subdomains.
Evidence of a hijack is found in change records: DNS answers that differ from your register, registrar audit logs showing logins and modifications, certificates you did not request for your own names. Response is an account-security incident — freeze with the registrar, revert from known-good records, rotate every credential that touched the control plane, review what mail and traffic were diverted. Prevention lives at the account layer: locks, strong 2FA, consolidated ownership, and change alerts on your own DNS.
Spoofing: the attacker claims your name, holds nothing
Spoofing is forgery rather than seizure. The attacker sends email with your exact domain in the From field from their own servers, counting on receivers to deliver mail without verifying authorisation. They control nothing of yours; the attack works only where the internet's courtesy — accepting claims at face value — has not been replaced by checks. Historically that was everywhere. Increasingly it is only where the domain owner has not published enforcement.
That is what makes spoofing the most completely solvable of the three. DMARC at p=reject, backed by aligned SPF and DKIM, instructs receivers to refuse forgeries of your exact domain, and major receivers obey. The evidence lives in your DMARC aggregate reports — every spoofing attempt enumerated by source — and the fix lives in your own DNS records. When a brand says 'anyone can email as us', that is a configuration confession, not a fact about the internet.
Lookalikes: the attacker builds next door
Lookalike impersonation sidesteps your domain completely. The attacker registers a neighbouring name — typo, homoglyph, combo, different TLD — and builds there: real DNS, real certificates, real authentication that passes every check, because every check is honestly satisfied for the attacker's own domain. Nothing is seized and nothing is forged; the deception is purely human, aimed at eyes that read quickly and systems that assume rather than verify.
Consequently the defenses are the observational ones: monitoring registrations, certificates, and DNS arming to find the neighbours early; takedown through abuse channels to remove them; defensive registration to own the best plots; and process controls like payment callbacks that refuse to trust any domain-based claim about money. DomainGuard exists for this third category primarily — its checks report lookalike registrations, certificates and DNS-arming signals around your domain, because a complete picture needs all three columns. It does not grade your own DMARC, SPF or DKIM setup.
Why the confusion costs money
Misdiagnosis misallocates the response. Teams suffering lookalike phishing have bought registrar-lock upgrades (a hijack control) and wondered why the attacks continued. Teams being spoofed have paid for takedown services against domains that did not exist, while their own p=none record sat unpublished-enforced for a year. And genuine hijacks — the rarest and most serious — have been initially dismissed as 'another phishing site', losing the first hours in which a registrar freeze is easiest.
The triage question that separates the three takes ten seconds: whose domain is actually involved? If the address in the incident is character-for-character yours, ask next whether your DNS still says what you set — no means hijack, yes means the incident is spoofed mail or a copied site on someone else's hosting claiming your name in content only. If the address differs by any character, it is a lookalike, whatever the page on it claims. Write that question at the top of your incident template; it routes everything downstream correctly.
One estate, three budgets
Mature programs fund all three columns proportionately to their risk. Hijack prevention is nearly free and non-negotiable: locks, 2FA, a register, change alerts. Spoofing elimination is a project with a finish line: the DMARC track, weeks of attention, then maintenance. Lookalike defense is the standing operation: monitoring subscriptions, takedown time, defensive renewals — a permanent, modest operating cost because the namespace next door to your brand is permanent and public.
Reviewed quarterly, the three columns make a one-page posture: hijack controls verified on this date, spoofing posture at reject with this quarter's blocked-forgery count from the reports, lookalikes found/armed/removed this quarter. That page, more than any single tool, is what 'we take domain security seriously' looks like when it is true — and it is achievable, in full, by a company of ten people.
Five actions to take today
- Classify every incident first: is the involved domain exactly yours, and if so, does your DNS still match your records?
- Hijack column: registrar and DNS accounts locked, 2FA-protected, consolidated, with change alerts on your own names.
- Spoofing column: DMARC enforced at p=reject with aligned SPF and DKIM, and aggregate reports reviewed monthly.
- Lookalike column: continuous registration and CT monitoring, defensive registrations, and a rehearsed takedown ladder.
- Summarise all three columns on one quarterly posture page with dates and counts.
Worked example: one brand, three different incidents in a year
A fictional services firm, Harbor Lane Accounting (6 domains monitored), met all three in a single year. In March, aggregate reports showed 900 spoofed messages using its exact domain — closed permanently by the move to p=reject. In July, a lookalike with MX records ran a bank-detail attempt — stopped by the callback rule and suspended in 9 days. In October, a CT alert revealed a certificate for its real subdomain issued after a dormant vendor delegation was exploited — a hijack-path incident, contained by reclaiming the delegation and rotating DNS account credentials. Three headlines a newspaper would phrase identically; three utterly different responses, each correct because the first triage question was asked.
FAQ
Our customers got phishing from a domain like ours. Which attack is it?
If the domain differs by any character — a letter, a hyphen, an extension — it is a lookalike, regardless of how perfect the page looks. Your response is monitoring-led takedown plus customer warning.
Can DMARC stop DNS hijacking?
No. DMARC governs mail authentication claims; a hijack changes the records themselves, including potentially the DMARC record. Hijack defense is account security, locks, and change monitoring on your own DNS.
How do we detect a hijack quickly?
Watch your own names: alert on nameserver, MX, and A-record changes and on certificates issued for your domain from unexpected CAs. DomainGuard includes own-domain change signals alongside lookalike monitoring for this reason.
Is spoofing still common given DMARC exists?
Attempts are constant; success depends on the target domain's enforcement. Attackers probe the _dmarc record first — an enforced domain is simply skipped for a softer one, which is the best argument for finishing your own rollout.
Which of the three should a small company fix first?
Spoofing, because it has a finish line and you control it entirely; hijack hygiene in the same week because it is nearly free; lookalike monitoring as the standing layer you then keep.