·
2 min read
What a takedown status should tell you
A useful takedown status shows where a case was filed, when, the provider's response, whether it is still live and what happens next.
ChainPatrol Team
A status that says “in progress” tells you nothing. A status that says “filed with registrar and host on the 3rd, host acknowledged on the 4th, content still live, next re-file on the 8th” tells you everything, including whether to worry.
The fields
Field | Why it matters |
|---|---|
Where it was filed | Registrar, host, proxy or platform, which tells you which clock you are waiting on |
When | Timestamps let you compute your own medians |
Route | API, web form or email, which tells you how fast to expect a response |
Provider response | Acknowledged, declined with reason, or silent |
Still live? | The field most vendors omit |
Blocked? | Whether customers are protected meanwhile |
Next step and date | Re-file, escalate, review |
Reviewed by a person? | And why |
In a report
A good report aggregates the same fields. Removed, blocked with takedown in progress, still live, and waiting on you. A report that only counts removals hides the cases that still put customers at risk. See reporting and the sample takedown report.
The test
Ask a vendor for a still-live list from last month with reasons. If they can produce it, the status model is real.
Frequently asked questions
Why would a vendor hide still-live cases?
They make the report look worse. They also make it honest.
Can status be pushed to our tools?
Yes. Webhooks push status updates to your tools, and the API lets you pull status on demand. See developers.
Want to see what is already out there? Get a free scan or book a demo.
Fakes of your brand already out there?
ChainPatrol finds them, blocks the links in wallets and browsers, and files the takedowns for you.
More from The Impersonation Institute
What automated takedowns are, and what they can't do
Automated takedowns file and follow up removal requests without a person. What's automated, what can't be, and how to spot a relabeled manual queue.
ChainPatrol Team
Automation and takedown mechanics
What is an automated takedown?
An automated takedown is a removal request a system files and follows up without a person. Short definition, the four steps, and what automation can't do.
ChainPatrol Team
Automation and takedown mechanics
What is human-in-the-loop brand protection?
People decide some cases and automation decides the rest. What matters is which cases, and whether the vendor names them. Definition and how to evaluate it.
ChainPatrol Team
Automation and takedown mechanics