← Go back

Live vs Dormant Lookalike Domains: Which Is Dangerous?

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

The short answer

The live one, today: a resolving lookalike is impersonating now and scores 80 without a certificate, 90 with one. A dormant registration scores 40–50 — not dangerous this hour, but confirmed inventory that can activate in minutes. The priority scale exists so a small team files on the live threat first and watches the dormant ones instead of treating every hit as the same emergency.

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

What is live versus dormant lookalikes?

Live and dormant describe the two states a registered lookalike can be in: resolving — DNS points it at a server that answers — or non-resolving, registered but serving nothing. TakedownCoop's scanner derives the state from its DNS check and encodes it in the priority score every hit carries.

What is live versus dormant lookalikes?

Live and dormant describe the two states a registered lookalike can be in: resolving — DNS points it at a server that answers — or non-resolving, registered but serving nothing. TakedownCoop's scanner derives the state from its DNS check and encodes it in the priority score every hit carries.

The scan behind this page works in one pass over your whole street. It generates typosquat, homoglyph, affix and TLD-swap candidates from your domain, checks every one against real DNS resolution, searches Certificate Transparency logs for lookalike certificates, and tries a public, no-login check for fake profiles using your exact brand handle. For live versus dormant lookalikes, that means the first artefact you work from is evidence — what resolved, what holds a certificate, what could not be checked — rather than a screenshot someone sent you.

How the scan ranks and records it

Prioritisation is built into the result list. A hit that resolves and holds a certificate scores 90; resolving without a certificate, 80; registered but not resolving, 50 with a certificate and 40 without; a name seen only in Certificate Transparency logs scores 35, or 30 when it neither resolves nor is registered. You therefore deal with live versus dormant lookalikes in the order an impersonator would exploit it — live doors first — while the scan states plainly which checks it could not perform.

One scale, two correct responses

The scale's genius is administrative, not technical. A scan that returned twelve undifferentiated 'threats' would either panic a small team into filing on all twelve — wasting the host filings on names with no host content — or train them to ignore the list entirely. Scores force the sequence: 80s and 90s are this week's filings; 40s and 50s are monitoring entries; 35s and 30s are CT signals to keep in the record.

State is also temporary in both directions. A live site can be suspended mid-filing and look dormant at the re-check — which is why the case system verifies resolution by re-scan rather than by a provider's say-so — and a dormant name can light up overnight. The seven-day recheck after submission, and monitoring beyond it, exist because the live/dormant line is a snapshot, and the product never pretends otherwise.

A worked example, end to end

A fictional gym, Forge Athletics at forgeathletics.com, scans to six hits: two live (90 and 80), three dormant (50, 40, 40) and one CT-only (35). The owner files registrar and host packets on the two live names in week one, opens monitoring on the rest, and closes nothing on a provider's word. At the post-submission recheck, one live name has stopped resolving — verified by re-scan, case resolved — while a formerly dormant 40 has activated and arrives as a re-opened case at 90, already documented.

Turning evidence into a filing

A complaint says 'this is fake'; a packet proves it. The Pro packet generator turns a confirmed hit into a channel-correct evidence packet — one for the registrar, one for the host, and separate ones for Meta, Google Ads, marketplaces and app stores where they apply — each with a filing checklist written for that channel. The honesty rule is printed in every packet: TakedownCoop prepares the evidence and never claims to submit to a channel it cannot actually submit to. Filing stays with you or your agent, which is also why the evidence has to stand on its own.

  1. Sort every scan's hits by priority before deciding anything
  2. File registrar and host packets on resolving hits (80–90) first
  3. Never file a host report on a name that does not resolve — there is nothing to suspend
  4. Place dormant (40–50) and CT-only (30–35) hits on monitoring
  5. Verify every claimed resolution by re-scan, because states change both ways

After you file: tracking the case

What happens next is tracked, not hoped for. Each target becomes a case — domain, fake store, social profile or scam ad — moving through evidence collected, packet built, submitted, provider response, resolved or reappeared. TakedownCoop distinguishes what you attest (that you submitted, that a provider replied) from what is verified by re-scan (that the item is actually gone), and it schedules a recheck seven days after a case is submitted so silence from a provider becomes a prompt, not a dead end.

Where efforts like this usually go wrong

A second failure is overreach — padding a filing with suspicions the evidence does not carry. TakedownCoop's scan is careful to separate what it confirmed from what it could not check, and a filing should inherit that discipline exactly: claim the resolving domain, the certificate, the screenshots you actually hold, and stop there. Reviewers act fastest on filings whose every sentence they can verify, and a single inflated claim taxes all the true ones beside it.

Finally, do not let a win delete the record. Brands that close a takedown by celebrating and clearing the folder meet the reappearance defenceless; brands that keep the case — evidence, tickets, verified resolution and all — meet it with precedent. In this product the record is not paperwork after the work. Kept properly, it is most of the work, because the second filing is always the one that ends the pattern.

Keeping it from coming back

Closing the loop matters because clones come back under new names and new accounts. Re-appearance monitoring re-scans and regenerates packets; the verified-genuine page lets a cautious customer verify your real door before paying anyone; and the case timeline — every event, in order — exports as JSON or CSV when a processor, insurer or marketplace asks how you handled it. That is the co-op model applied to live versus dormant lookalikes: walk the street, knock with evidence, keep watch.

Frequently asked questions

What are the exact priority scores?

90 resolving with a certificate; 80 resolving without; 50 registered with a certificate; 40 registered without; 35 CT-only discovery; 30 certificate record standing alone.

A dormant name worries me more than a live one. Reasonable?

The live one is taking customers today. File it first; the dormant one's risk is future activation, which monitoring covers.

Can a live lookalike go dormant to dodge a filing?

It can stop resolving, but the registration and the evidence persist, the registrar channel still applies, and monitoring catches reactivation.

Who decides a case is resolved — the provider or the scan?

The scan. Resolution counts as verified only when a re-scan confirms the item is gone; provider replies are recorded as attestations.

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