Security snapshot
Across 2 brideliness-child 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 usernames100%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 2 indexed WordPress sites with brideliness-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 100% versus 38.6% overall (+61.4 percentage points).
Header-grade F is 100% vs 82.6% overall (+17.4 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 brideliness-child, 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 | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| f*n*a*t*a*n*i*g*y*o*d*.com (WP 7.0.4) | — | F | Sep 8, 2026 | |
| c*y*t*l*r*d*.com (WP 7.1) | — | F | Aug 31, 2026 |
Page 1 of 1