โ† Go back

How Do Priority Scores Rank Lookalike Hits?

Published 2026-11-14 ยท Reviewed 2026-11-14 ยท By the Ingenious AI team

The short answer

By state, not by suspicion. 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 Certificate Transparency discovery scores 35, and a certificate record standing alone 30. The scale is the scanner's own arithmetic, and it dictates your order of work: file the 80s and 90s, watch the rest.

Run the free brand scan โ€” one domain, no account, no card

What is priority scores?

A priority score is the number the scanner assigns each confirmed hit from two observed facts โ€” does it resolve, and does it hold a certificate โ€” plus its discovery source. It is deliberately not a risk model trained on opinions: every score can be re-derived from the DNS and CT evidence printed beside it in the results and the packet.

What is priority scores?

A priority score is the number the scanner assigns each confirmed hit from two observed facts โ€” does it resolve, and does it hold a certificate โ€” plus its discovery source. It is deliberately not a risk model trained on opinions: every score can be re-derived from the DNS and CT evidence printed beside it in the results and the packet.

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 priority scores, 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 priority scores in the order an impersonator would exploit it โ€” live doors first โ€” while the scan states plainly which checks it could not perform.

Two facts, six scores, zero vibes

Resolution is the first fact because it separates the live from the latent: a resolving name can be visited, screenshotted, filed on with a host and verified closed. Certification is the second because it separates the prepared from the speculative: a certificate means someone provisioned HTTPS for the name, which impersonators do when a launch is intended and browsers demand a padlock. Cross the two facts and you get the four DNS scores โ€” 90, 80, 50, 40 โ€” in an order no reasonable filer would dispute.

The two CT scores handle the fifth situation: names reality revealed through the logs rather than through registration checks. A CT-only discovery โ€” a brand-containing name pulled from the logs that generation missed โ€” scores 35, and a certificate record that stands entirely alone scores 30. They sit below dormant registrations because a log entry is preparation, not presence; they sit on the list at all because preparation, watched, is the cheapest warning a brand ever gets.

A worked example, end to end

A fictional brewery, Stone Bridge Brewing at stonebridgebrewing.com, prints its first scan on one page: 90 โ€” the TLD-swap clone, live and certified; 80 โ€” an affix store, live; 50 โ€” a deletion variant, dormant but certified; 40 โ€” a transposition, dormant; 35 โ€” a CT discovery nobody had generated. The week's work writes itself from the numbers: two filings, two monitoring entries, one name added to the watch record โ€” and when the owner reports to the brewery's partners, the scores are the agenda.

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. Memorise the ladder: 90 live+certified, 80 live, 50 dormant+certified, 40 dormant, 35 CT discovery, 30 CT only
  2. File in score order โ€” the ladder is the work plan
  3. Add every sub-80 hit to monitoring rather than discarding it
  4. Quote scores alongside evidence in partner and client reports
  5. Re-score on every re-scan; movement up the ladder is the alert

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

The commonest failure with priority scores 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

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 priority scores: walk the street, knock with evidence, keep watch.

Frequently asked questions

Where do the scores come from?

The scanner itself: resolution and certificate status from its DNS and CT checks, computed per hit and sorted live-first.

Is 90 always the worst threat?

It is the most complete attack profile the scan can observe โ€” live and certified. A live 80 taking payments can still deserve same-day filing; the ladder orders work, it does not ration it.

Why is a dormant certified name (50) above a dormant plain one (40)?

Because the certificate shows preparation for launch. Provisioning HTTPS is a step taken by someone intending the name to be visited.

Do scores appear in the packets?

Yes โ€” the priority score is part of the evidence block every packet carries.

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