← Go back

What Is a Homoglyph Domain?

Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team

The short answer

A homoglyph domain replaces one character of your brand with a visually identical or near-identical one — the letter l with the digit 1, o with 0, or the pair rn arranged to read as m. The name looks correct to a human eye while being a completely different registration. TakedownCoop's generator builds homoglyph swaps for every applicable letter and checks them against DNS and CT logs.

Run the free brand scan — one domain, no account, no card

What is homoglyph domains?

Homoglyphs are characters that render alike. In domain names they are the most deceptive squat family because the fraud is optical: the victim can stare at the address bar and still see their brand. Detection therefore cannot rely on looking — it has to be systematic, generated from a swap table and verified against registration data.

What is homoglyph domains?

Homoglyphs are characters that render alike. In domain names they are the most deceptive squat family because the fraud is optical: the victim can stare at the address bar and still see their brand. Detection therefore cannot rely on looking — it has to be systematic, generated from a swap table and verified against registration data.

Detection starts with the free scan on TakedownCoop's home page. From your one genuine domain, the scanner builds the candidate set an impersonator would plausibly register — typosquats made by deleting, transposing, duplicating or substituting letters, homoglyph lookalikes, affix combinations, and TLD swaps — and tests each candidate against live DNS. That order matters for homoglyph domains: generation first, evidence second, and nothing is called a hit until DNS or a certificate log says it is real.

How the scan ranks and records it

The results are ranked, not dumped. The scanner's own priority scores put a resolving lookalike with a certificate at 90 and one without at 80, registered-but-dormant names at 50 or 40 depending on whether a certificate exists, and CT-only discoveries at 35 or 30. Certificate Transparency evidence is filtered for relevance — shared certificates carrying unrelated names are not treated as evidence against your brand — and any check that could not be performed is reported as exactly that, never converted into a reassuring claim.

Why your eyes are the wrong tool for this family

Every other typo family makes an error you could in principle spot. Homoglyphs are engineered so that you cannot: at address-bar sizes, in the fonts browsers use, the substituted character is the brand letter for all practical purposes. Telling staff or customers to 'check the URL carefully' is therefore not a defence against this family — the check that works is the mechanical one, a generator with a homoglyph table walking every position of your name.

The scanner's homoglyph map swaps each replaceable letter for its lookalikes and labels the results 'homoglyph', a label the packet preserves. That precision helps at the registrar: a homoglyph registration is difficult to explain as coincidence or legitimate use, and abuse desks know the technique by name. When the hit also resolves and holds a certificate — priority 90 — it is the strongest evidence profile the scan produces.

A worked example, end to end

A fictional pharmacy, Remedica at remedica.com, scans and finds rernedica.com — the m rendered as r+n — resolving to a store selling the pharmacy's best-known products at steep discounts, certificate in place, priority 90. Staff shown the two names side by side in a meeting pick the wrong one twice. The owner files registrar and host packets the same day, and the verified-genuine page becomes the answer the pharmacy prints on its bags: check the real door here, because your eyes cannot.

Turning evidence into a filing

Evidence only helps if it arrives in the shape the channel expects. TakedownCoop's packet generator produces one packet per channel — registrar, host, Meta, Google Ads, marketplace, app store — each with that channel's own subject line and filing checklist, built on the same evidence block: genuine brand, lookalike domain, detection method, DNS and CT evidence, and priority. Packets are a Pro feature ($49/mo; Agency $99/mo covers multiple client brands), and they are prepared for the brand owner or their authorised agent to file.

  1. Scan so every homoglyph swap in the table is generated and checked
  2. Treat a resolving homoglyph as top priority — it is built to be invisible
  3. File registrar and host packets with the swap spelled out character by character
  4. Give customers the verified-genuine page instead of telling them to eyeball URLs
  5. Keep the homoglyph label in the evidence for escalation

After you file: tracking the case

The follow-through is where most takedowns quietly die, so the product tracks it as a case. States run from evidence collected through packet built, submitted and provider response, to resolved — and a case can be re-opened as reappeared when monitoring finds the same threat back. Submitted and provider-response states are recorded as holder attestations, honestly labelled, while a verified resolution needs a re-scan showing the target is gone. The recheck after submission is set at seven days.

Where efforts like this usually go wrong

The commonest failure with homoglyph domains is treating it as a message instead of a case. A report typed from memory, sent from the wrong account, missing its ticket number within the week — each is a small thing, and together they are why impersonators outlast brands that were right about everything. The artefacts exist to remove memory from the loop: the evidence block is generated, not recalled; the checklist is written for the channel, not improvised; the case holds the IDs, not an inbox thread nobody can find in month two.

There is also a sequencing mistake: acting on the loudest artefact instead of the highest-priority one. A furious customer message about a dormant name feels urgent; a quiet scan result showing a live, certified clone is urgent. The priority score exists to arbitrate exactly that conflict — 90 before 40, live before loud — and the teams that follow it spend their filing hours where the money is actually leaving.

Keeping it from coming back

Impersonators rotate, so a one-off filing is a snapshot, not a solution. Monitoring re-scans the domain, and when a known threat reappears the case re-opens and its packet regenerates. Pair that with the verified-genuine page — a public page where customers can confirm they are dealing with the real brand — and the timeline export (JSON and CSV) that processors and insurers ask for, and homoglyph domains stops depending on whoever happens to notice the fake next.

Frequently asked questions

What characters do homoglyph swaps use?

Lookalike substitutions from the scanner's homoglyph map — for example digit-for-letter swaps and multi-character renderings that read as a single letter.

Can customers be trained to spot them?

Not reliably — that is the point of the technique. The defence is systematic detection plus a verified-genuine page customers can check.

Is a homoglyph registration ever innocent?

The packet does not argue motives; it presents the registration, the resolution and the content. But a visual-clone name resolving to a clone store is a pattern abuse desks recognise.

How are homoglyph hits scored?

By the universal scale: 90 resolving with certificate, 80 resolving without, 50/40 registered-only, 35/30 CT-only.

Keep exploring

TakedownCoop home — run the free brand scan · All TakedownCoop guides · Pricing — Free, Pro and Agency · Get a license key · Takedown cases · My street (dashboard) · Terms · Privacy · Ingenious AI — all platforms

Related guides