← Go back

How Do You File a Registrar Abuse Report for a Lookalike Domain?

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

The short answer

Find the lookalike's registrar of record with an RDAP lookup, then file through that registrar's own abuse form or email with your trademark or first-use evidence and a complete evidence block attached. Keep the ticket number — your host and platform reports will cite it — and re-check resolution after 72 hours; if the name still resolves, escalate with the hosting packet.

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

What is a registrar abuse report?

A registrar abuse report is the complaint filed with the company that registered a lookalike domain, asking it to act on an impersonation or phishing registration. It is the first channel in TakedownCoop's packet generator because the registrar controls the name itself, and its ticket number anchors every later filing with hosts and platforms.

What is a registrar abuse report?

A registrar abuse report is the complaint filed with the company that registered a lookalike domain, asking it to act on an impersonation or phishing registration. It is the first channel in TakedownCoop's packet generator because the registrar controls the name itself, and its ticket number anchors every later filing with hosts and platforms.

TakedownCoop's free brand scan is where a registrar abuse report stops being a suspicion and becomes a record. You enter one domain — no account, no card — and the scanner generates dozens of lookalike candidates from your brand name: deleted-letter, transposed-letter, duplicated-letter and keyboard-neighbour typosquats, homoglyph swaps, affix squats built from prefixes and suffixes, and the same name on different top-level domains. Every candidate is then checked against real DNS resolution, so a name that merely exists on paper is never reported as a live threat.

How the scan ranks and records it

Certificate Transparency is the scan's second witness. When a lookalike holds a publicly logged certificate, the scan records it, and names that appear in the logs but were never generated as candidates are added as CT discoveries. Hits are then prioritised the way a small team needs them: a live, resolving lookalike with a certificate scores 90, a live one without a certificate 80, a registered but non-resolving name 50 with a certificate or 40 without, and a certificate-only discovery 35 or 30. Live threats are filed first; dormant registrations are watched, not panicked over.

What the registrar packet actually contains

The registrar packet's subject line names the pattern plainly: an abuse report about an impersonation or phishing lookalike domain, with the candidate domain in the subject. Inside, the evidence block states your genuine brand and domain, the lookalike, how the scan detected it, whether it resolved at scan time, the Certificate Transparency and DNS evidence, and the hit's priority score — the facts a registrar's abuse desk needs before it will open a case.

Its filing checklist is short and ordered. Confirm the registrar via RDAP and use that registrar's own abuse route, not a generic web form. Attach trademark registration or first-use evidence. Include the evidence block verbatim and add dated screenshots if the site resolves. Keep the ticket number. Then re-check after 72 hours — that re-check is a step in your workflow, not a promise the registrar acts within 72 hours.

A worked example, end to end

A fictional Belize tour operator, Maya Reef Tours at mayareef.com, finds mayareef-tours.com resolving to a booking page copying its logo. Its scan scores the hit 90 — live, with a certificate. The owner runs an RDAP lookup, confirms the registrar, and files the registrar packet the same afternoon with the trademark filing and two dated screenshots. The registrar replies with ticket AB-4471. At the 72-hour re-check the page still resolves, so the owner files the host packet next, citing AB-4471 in the first paragraph.

Turning evidence into a filing

Finding the problem is only the first third of the work. On Pro ($49/mo) and Agency ($99/mo), each confirmed hit can generate a takedown packet: a complete, channel-correct evidence packet with a filing checklist written for the specific channel — registrar abuse desk, hosting provider, Meta, Google Ads, marketplaces or app stores. The packet carries the genuine brand and domain, the lookalike, how it was detected, whether it resolved at scan time, the DNS and Certificate Transparency evidence, and the priority score, so the person receiving it does not have to take your word for anything.

  1. Confirm the lookalike's registrar via an RDAP lookup and use that registrar's own abuse form or email
  2. Attach your trademark registration or first-use evidence for your brand
  3. Include the evidence block verbatim; add dated screenshots of the live site if it resolves
  4. Keep the registrar's ticket number — cite it in host and platform reports
  5. Re-check resolution after 72 hours; if still live, escalate with the host packet

After you file: tracking the case

After filing, the case — not your inbox — is the system of record. TakedownCoop's case tracking follows each target through evidence collected, packet built, submitted, provider response recorded, resolved, and, if the impersonator returns, reappeared and re-opened. Two of those states are labelled as holder attestations, because the product records what you report about a submission or a provider's reply; a resolution only counts as verified when a re-scan confirms the item is actually gone. A submitted case is scheduled for recheck seven days after submission.

Where efforts like this usually go wrong

The commonest failure with a registrar abuse report 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

The last step is keeping the street watched. Re-appearance monitoring on Pro and Agency re-scans your domain and regenerates packets when an impostor returns, instead of waiting for a customer to find the fake first. The public verified-genuine page gives customers a door they can check — one page that confirms they are at your real business — and the evidence timeline exports as JSON or CSV for payment processors and insurers. Dealt with once, a registrar abuse report is an incident; watched continuously, it becomes a routine.

Frequently asked questions

Does TakedownCoop file the registrar report for me?

No. TakedownCoop prepares the complete packet and checklist; the brand owner or their authorised agent files it. Every packet states this plainly.

What if I do not have a registered trademark?

The packet checklist accepts trademark registration or first-use evidence. Use whichever you genuinely have — registration documents, or dated proof you traded under the name first — and do not claim a registration you do not hold.

Why does the ticket number matter so much?

Because the host and platform packets cite it. A registrar ticket shows the other channels the case is real, sequenced and already in motion.

What happens at the 72-hour re-check?

You check whether the lookalike still resolves. If it does, the registrar checklist's own next step is to escalate with the hosting provider packet.

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