Security snapshot
Across 5 conary 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 usernames60%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 conary, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 60% versus 38.5% overall (+21.5 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 conary, 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 |
|---|---|---|---|---|
| d*n*e*h*a*r*l*.com (WP 7.1) | — | F | Sep 6, 2026 | |
| a*t*w.com (WP 6.9.1) | — | F | Sep 1, 2026 | |
| u*s*i*a*i.fi (WP 6.9.1) | — | F | Aug 7, 2026 | |
| d*j*n*e*r*p*.cz (WP 7.0.2) | — | F | Aug 5, 2026 | |
| l*a*n*o*c*n*r*s*.com | — | F | Jul 21, 2026 |
Page 1 of 1