Security snapshot
Across 4 sharf WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 75%
Grade B 0%
Grade C 0%
Grade D 0%
Grade F 25%
Fail the header check (F)25%vs 82.6% avg
Leak usernames50%vs 38.6% avg
Expose a sensitive file25%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 4 indexed WordPress sites with sharf, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 25% versus 82.6% overall (-57.6 percentage points).
Sensitive-file exposure is 25% vs 1.8% overall (+23.2 pp); Username enumeration is 50% vs 38.6% overall (+11.4 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp).
These are observational associations among sites where TLDWP detected sharf, 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 |
|---|---|---|---|---|
| s*a*f*o*e*.ru | 1.0.0· 100% conf. | F | Sep 9, 2026 | |
| p*o*e*t*s*o*i*t*c*s.com (WP 7.1) | — | A | Aug 22, 2026 | |
| h*l*s*a*f.com (WP 7.0.2) | — | A | Jul 20, 2026 | |
| h*l*s*h*r*f.com (WP 7.0.2) | — | A | Jul 20, 2026 |
Page 1 of 1