Security snapshot
Across 6 bc-couples 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.6% avg
Leak usernames33%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with bc-couples, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.6% overall (+17.4 percentage points).
Username enumeration is 33.3% vs 38.6% overall (-5.3 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected bc-couples, 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
6
| Domain | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| b*o*s*i*e*a*s.com (WP 7.1) | — | F | Sep 5, 2026 | |
| e*o*y*a*s*o*.com (WP 7.1) | — | F | Sep 5, 2026 | |
| n*b*e*c*m*.com (WP 7.1) | — | F | Aug 30, 2026 | |
| q*i*k*s*x.com (WP 7.1) | — | F | Aug 29, 2026 | |
| l*v*c*m*e*l*.com (WP 7.1) | — | F | Aug 28, 2026 | |
| g*-*u*z.com (WP 7.1) | — | F | Aug 27, 2026 |
Page 1 of 1