Security snapshot
Across 5 sbhc-event-client WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 100%
Grade C 0%
Grade D 0%
Grade F 0%
Fail the header check (F)0%vs 82.5% avg
Leak usernames0%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 5 indexed WordPress sites with sbhc-event-client, 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 0% vs 38.5% overall (-38.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 sbhc-event-client, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| r*s*e*o*e*y.com (WP 7.1) | B | Sep 8, 2026 | |
| s*m*i*b*c.com | B | Sep 5, 2026 | |
| n*r*h*r*p*t*r*c*v*r*.com (WP 7.1) | B | Sep 1, 2026 | |
| r*l*i*h*a*s*h.com (WP 7.1) | B | Aug 31, 2026 | |
| w*l*i*g*a*.com (WP 7.1) | B | Aug 26, 2026 |
Page 1 of 1