Security snapshot
Across 2 egovenz-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 100%
Grade B 0%
Grade C 0%
Grade D 0%
Grade F 0%
Fail the header check (F)0%vs 82.5% avg
Leak usernames50%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 2 indexed WordPress sites with egovenz-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 0% versus 82.5% overall (-82.5 percentage points).
Username enumeration is 50% vs 38.5% overall (+11.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 egovenz-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
.gov.jm
2
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| j*a.g*v.jm (WP 6.6.2) | A | Sep 8, 2026 | |
| j*c*s*o*s.g*v.jm (WP 6.6.2) | A | Jul 20, 2026 |
Page 1 of 1