Security snapshot
Across 6 block-options-fork 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.5% avg
Leak usernames17%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with block-options-fork, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 16.7% versus 38.5% overall (-21.8 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.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 block-options-fork, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| s*a*p*o*s*s*a*e*.ca (WP 7.0.4) | F | Sep 5, 2026 | |
| s*a*g*l*m*r*c*.ca (WP 7.0.4) | F | Sep 5, 2026 | |
| s*a*p*o*s*s*h*r*h.ca (WP 7.0.4) | F | Sep 5, 2026 | |
| w*n*s*r*e*i*a*e*a*i*h*s.ca | F | Aug 21, 2026 | |
| a*s*m*t*o*c*r*s.ca | F | Aug 21, 2026 | |
| a*s*m*t*o*p*r*s*.ca | F | Jul 28, 2026 |
Page 1 of 1