Security snapshot
Across 5 blossom-pin-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 20%
Grade B 0%
Grade C 0%
Grade D 20%
Grade F 60%
Fail the header check (F)60%vs 82.6% avg
Leak usernames80%vs 38.6% avg
Expose a sensitive file20%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 5 indexed WordPress sites with blossom-pin-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 80% versus 38.6% overall (+41.4 percentage points).
Header-grade F is 60% vs 82.6% overall (-22.6 pp); Sensitive-file exposure is 20% vs 1.8% overall (+18.2 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp).
These are observational associations among sites where TLDWP detected blossom-pin-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
5
| Domain | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| n*o*a*i*s*r*.com | — | D | Sep 1, 2026 | |
| e*p*o*-*r*v*i*.com (WP 7.1) | — | F | Aug 28, 2026 | |
| e*b*u*e*r.com (WP 7.1) | — | F | Aug 27, 2026 | |
| c*a*t*t*r*.com (WP 7.0) | — | A | Aug 16, 2026 | |
| s*e*h*n*e*u*l*.com | — | F | Jul 23, 2026 |
Page 1 of 1