Scam SentryHost / Registrar Abuse Reports (Rolling 90 day stats)
| Entity | Domains Reported | Total Reports | Repeat Reports ⓘ |
|---|---|---|---|
| Colocrossing.com | 11 | 11 | 0% |
| Alibaba Cloud | 4 | 4 | 0% |
| Alibaba Cloud | 10 | 10 | 0% |
| GoDaddy | 4 | 4 | 0% |
| GoDaddy | 4 | 4 | 0% |
| Namesilo.com | 28 | 29 | 3% |
| Spaceship.com | 12 | 14 | 14% |
| Amazon Web Services | 14 | 19 | 26% |
| Namecheap.com | 80 | 108 | 26% |
| Cloudflare | 112 | 192 | 42% |
| Dreamhost.com | 17 | 35 | 51% |
| Internet.bs | 26 | 62 | 58% |
Trends Revealed in Registrar Abuse Response Stats
The registrar stats uncovers trends in scam takedown compliance. Most notably, Amazon Web Services and Hi-load.biz at the bottom extreme, with a high repeat-report rate. Over half of all abusive domains needed multiple reports before any action was taken, while Internet.bs and GoDaddy follow closely.
Most abuse reports require re-reporting, allowing abuse to go unchecked for days or weeks, underscoring persistent gaps in domain registrar enforcement and ICANN abuse policy.
Green Sets the Standard
In contrast, registrars with a 0 % multiple-report rate highlights the impact of swift abuse takedowns. The abuse reporting trends tend to show better response times from smaller registrars, typically with in-house abuse teams. Smaller registrars can honor aggressive SLAs with near-instant takedowns and virtually no repeat filings, thanks to leaner portfolios, strict onboarding/KYC (know your customer) checks and dedicated compliance staff.
Large Registrars Struggle with Abuse Reporting Loads
Large registrars juggle millions of active domains and farm out abuse desks to third-party vendors with quantity prioritized over quality. This approach dilutes accountability, creates sprawling ticket backlogs and requires multiple abuse reports before a bad actor is finally placed on clientHold status.