โ† Go back

Registrar or Host: Which Takedown Should You File First?

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

The short answer

Start with the registrar when you can: it controls the name itself, and its ticket number strengthens every later filing. You do not have to wait, though โ€” the host packet can be filed immediately, and the registrar checklist's own escalation step says to bring the host in if the name still resolves after 72 hours. Sequence them so each filing cites the other.

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

What is filing order โ€” registrar or host first?

The registrar-versus-host question is the ordering problem between the two infrastructure channels in a takedown: the registrar of record, which sold and controls the lookalike domain name, and the hosting provider, which serves the fake content from an IP address identified by the domain's A record.

What is filing order โ€” registrar or host first?

The registrar-versus-host question is the ordering problem between the two infrastructure channels in a takedown: the registrar of record, which sold and controls the lookalike domain name, and the hosting provider, which serves the fake content from an IP address identified by the domain's A record.

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 filing order โ€” registrar or host first: 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.

What each channel can actually switch off

A registrar action can suspend or transfer the name โ€” the fake loses its address everywhere at once. A host action removes the content, but the name survives and can be pointed at a new server within the hour. That asymmetry is why the registrar leads: it is the only filing that can retire the lookalike itself rather than one copy of what it serves.

The counter-argument is speed of evidence. The host can verify the impersonation from its own network โ€” the A record and the page it serves โ€” without waiting for anyone, and its packet needs nothing from the registrar to be complete. In practice the packets are designed to interlock: the host checklist asks for the registrar ticket number 'if already filed', and the registrar checklist names the host packet as its escalation. File the registrar first when both are ready; file whichever is ready rather than neither.

A worked example, end to end

A fictional jeweller, Auric & Vine at auricandvine.com, finds a live clone at auricandvine-shop.com, priority 90. Day one: the registrar packet goes in and returns ticket AV-881. Day two: the host packet follows, citing AV-881 and three screenshots. At the 72-hour re-check the name still resolves but the host has suspended the content, so the clone shows a suspension page while the registrar case continues โ€” the two filings divided the problem exactly as the checklists intend.

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. File the registrar packet first when it is ready โ€” it controls the name and issues the anchor ticket number
  2. File the host packet immediately after, citing the registrar ticket if you have it
  3. Include dated screenshots in the host filing while the site still resolves
  4. Re-check resolution after 72 hours and escalate whichever channel is still open
  5. Track both filings as linked cases with one evidence block

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

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

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 filing order โ€” registrar or host first stops depending on whoever happens to notice the fake next.

Frequently asked questions

Can I file both on the same day?

Yes. The registrar-first order is about anchoring โ€” the ticket strengthens the host filing โ€” not about a mandatory waiting period.

What if the registrar does nothing?

The registrar checklist's escalation step is the host packet. A host suspension removes the content even while the name dispute continues.

What if the host removes it but the domain stays registered?

The name can be re-pointed to a new host. Keep the registrar case open and let monitoring watch the domain for re-resolution.

Which channel does TakedownCoop prioritise in its packets?

The registrar packet is the generator's lead channel, and its checklist explicitly sequences the host escalation at the 72-hour re-check.

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