Security snapshot
Across 2 ami-disabled WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 100%
Grade D 0%
Grade F 0%
Fail the header check (F)0%vs 82.5% avg
Leak usernames0%vs 38.5% avg
Expose a sensitive file100%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 2 indexed WordPress sites with ami-disabled, equivalent to 0% of the current WordPress dataset.
The largest measured difference is sensitive-file exposure: 100% versus 1.8% overall (+98.2 percentage points).
Header-grade F is 0% vs 82.5% overall (-82.5 pp); Username enumeration is 0% vs 38.5% overall (-38.5 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp).
These are observational associations among sites where TLDWP detected ami-disabled, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
Where these sites live — top 1 domain endings
.com
2
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| a*i*i*e*r*l*c*n*i*g.com | C | Sep 4, 2026 | |
| a*t*a*e*s*n*l.com | C | Jul 24, 2026 |
Page 1 of 1