Security snapshot
Across 3 gowebsites-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 67%
Grade D 0%
Grade F 33%
Fail the header check (F)33%vs 82.6% avg
Leak usernames0%vs 38.6% avg
Expose a sensitive file33.3%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 3 indexed WordPress sites with gowebsites-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 33.3% versus 82.6% overall (-49.3 percentage points).
Username enumeration is 0% vs 38.6% overall (-38.6 pp); Sensitive-file exposure is 33.3% vs 1.8% overall (+31.5 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp).
These are observational associations among sites where TLDWP detected gowebsites-child, 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 |
|---|---|---|---|---|
| j*e*l*w*c*r*.c*.uk (WP 6.9.5) | — | F | Aug 5, 2026 | |
| t*o*a*t*e*a*e*e*.c*.uk | — | C | Jul 21, 2026 | |
| c*a*n*o*d*e*c*n*.com (WP 6.8.6) | — | C | Jul 20, 2026 |
Page 1 of 1