Data
Registrar & Host Takedown Responsiveness Index
Takedown-speed marketing is unstandardized: vendors quote averages measured from different starting points, on different case mixes, with different definitions of done. This index publishes defined metrics instead — median time-to-acknowledgment and median time-to-resolution observed across real impersona.io cases, next to what providers themselves declare. Observed and declared numbers are never mixed.
According to impersona.io data, the Takedown Responsiveness Index compiles provider-declared takedown SLAs for 15 providers — registrars, hosts, CDNs, email-abuse desks and browser blocklists — with observed medians from real remediation cases published per provider as they accumulate.
Time to acknowledgment
Elapsed time between our takedown submission to a registrar or host and the first recorded acknowledgment from that provider.
Time to resolution
Elapsed time between submission and the case being resolved — the impersonating content taken down or otherwise neutralized.
Observed responsiveness
Medians across real impersona.io remediation cases, all customers combined. Providers appear once they have at least 3 measurable cases. Last updated 2026-06-09.
Observed data is still accumulating
We only publish a provider once it has at least 3 measurable cases, so no observed medians meet the bar yet. Rather than pad the table with estimates, we leave it empty — the provider-declared expectations below are clearly labeled as exactly that.
Provider-declared expectations
SLA expectations from provider documentation and community experience for the providers our remediation workflow integrates with. These are expectations, not guarantees — listed separately so they are never confused with observed data.
| Provider | Channels | Integration | Declared ack | Declared resolution | Reported success |
|---|---|---|---|---|---|
| Cloudflare (Registrar / Trust & Safety) | registrar | Live API (tested) | 4 h | 24 h | 85% |
| GoDaddy (Registrar Abuse API) | registrar | API (sandbox-tested) | 24 h | 3 d | 75% |
| Namecheap (Email Abuse Report) | registrar · email_abuse | Email (best-effort) | 2 d | 4 d | 65% |
| Porkbun (Email Abuse Report) | registrar · email_abuse | Email (best-effort) | 24 h | 2 d | 70% |
| Dynadot (Email Abuse Report) | registrar · email_abuse | Email (best-effort) | 24 h | 3 d | 65% |
| Cloudflare (Hosting / CDN Abuse) | host · cdn | API (sandbox-tested) | 4 h | 24 h | 80% |
| Fastly (Hosting / CDN Abuse) | host · cdn | Email (best-effort) | 24 h | 3 d | 70% |
| Akamai (Hosting / CDN Abuse) | host · cdn | Email (best-effort) | 24 h | 3 d | 70% |
| AWS CloudFront (Hosting / CDN Abuse) | host · cdn | Email (best-effort) | 2 d | 5 d | 60% |
| Vercel (Email Abuse Report) | host | Email (best-effort) | 12 h | 2 d | 80% |
| Netlify (Email Abuse Report) | host | Email (best-effort) | 24 h | 3 d | 75% |
| DigitalOcean (Email Abuse Report) | host | Email (best-effort) | 24 h | 3 d | 70% |
| Hetzner (Email Abuse Report) | host | Email (best-effort) | 24 h | 3 d | 70% |
| Google Safe Browsing (Web Risk) | browser_blocklist | API (sandbox-tested) | 1 h | 4 h | 90% |
| PhishTank (Community Blocklist) | browser_blocklist | API (sandbox-tested) | 2 h | 12 h | 85% |
Methodology
Observed metrics aggregate every Impersona remediation case with recorded submission timestamps, across all customers. Time-to-acknowledgment is the elapsed time between our takedown submission to a provider and that provider's first recorded acknowledgment. Time-to-resolution is the elapsed time between submission and case resolution. Values are medians in hours; each median is published only once at least 3 measurable cases exist for that specific metric — a provider whose acknowledgment or resolution sample falls below that threshold has that metric shown as unavailable rather than published. Only provider-level aggregates are released — never case, domain, or customer details. Declared figures are the SLA expectations from provider documentation and community experience that Impersona uses for routing; they are expectations, not guarantees, and are kept separate so observed and declared numbers are never mixed.
Frequently asked questions
What is the Takedown Responsiveness Index?
The Takedown Responsiveness Index is a public impersona.io dataset of defined takedown-speed metrics: median time-to-acknowledgment and median time-to-resolution observed across real impersona.io remediation cases, published next to provider-declared SLA expectations. It covers the registrars, hosts, CDNs, email-abuse desks and browser blocklists impersona.io routes takedown reports to, and observed and declared numbers are never mixed.
Where do the provider-declared takedown numbers come from?
Declared acknowledgment and resolution figures are SLA expectations taken from provider documentation and community experience, for each provider the impersona.io remediation workflow integrates with. They are expectations, not guarantees — third-party providers decide takedown outcomes. The index lists declared figures separately from observed data so the two are never confused.
Why are observed medians missing for some providers?
A provider’s observed medians are published only once it has at least 3 measurable remediation cases with recorded submission timestamps. Below that threshold the index shows nothing rather than padding the table with estimates. The index is young and sample sizes are still small, so early medians are directional rather than definitive and will firm up as cases accumulate.
How often is the Takedown Responsiveness Index updated?
The index is recomputed from live impersona.io case data, and the page refreshes its cache daily — matching the underlying API’s 24-hour cache window. The visible ‘Last updated’ date above the observed table comes from the dataset’s own timestamp, so you can always see how current the numbers are.
How should I cite the Takedown Responsiveness Index?
Cite it as the impersona.io Takedown Responsiveness Index with the URL https://impersona.io/takedown-index and the ‘Last updated’ date shown on the page. The dataset is free to access and is served from a public impersona.io API endpoint. When quoting an observed median, include that provider’s sample count (n) from the table.
See who would be handling your takedowns
Run a free brand check to find the lookalike domains targeting your brand — and which registrars and hosts they sit behind.