Security snapshot
Across 5 bifo WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 0%
Grade F 100%
Fail the header check (F)100%vs 82.5% avg
Leak usernames20%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 5 indexed WordPress sites with bifo, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 20% versus 38.5% overall (-18.5 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.5 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected bifo, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| a*s*o*g*o*p.com (WP 7.0.4) | — | F | Sep 4, 2026 | |
| n*m*l*g*t*n*.com (WP 7.0.4) | — | F | Aug 26, 2026 | |
| l*p*o*i*g*o*p.com | — | F | Aug 23, 2026 | |
| k*s*i*.c*m.ua | — | F | Jul 30, 2026 | |
| e*v*r*a*t.info (WP 5.2.14) | — | F | Jul 29, 2026 |
Page 1 of 1