Security snapshot
Across 7 silktide-consent-manager WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 43%
Grade D 0%
Grade F 57%
Fail the header check (F)57%vs 82.5% avg
Leak usernames43%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 7 indexed WordPress sites with silktide-consent-manager, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 57.1% versus 82.5% overall (-25.4 percentage points).
Username enumeration is 42.9% vs 38.5% overall (+4.4 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 silktide-consent-manager, 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 |
|---|---|---|---|---|
| h*k*m*r*.ee | — | F | Sep 8, 2026 | |
| s*i*e*r*w.com | — | C | Sep 2, 2026 | |
| n*s*p*o*t.com (WP 7.1) | — | F | Aug 30, 2026 | |
| g*o*e*i*c*s*i*g.com | — | F | Aug 25, 2026 | |
| s*w*o*.ee | — | C | Aug 15, 2026 | |
| v*v*j*.com (WP 6.2.9) | — | F | Jul 28, 2026 | |
| s*e*k*r*s*p*o*t.com | — | C | Jul 18, 2026 |
Page 1 of 1