Security snapshot
Across 4 come 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.6% avg
Leak usernames50%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 4 indexed WordPress sites with come, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.6% overall (+17.4 percentage points).
Username enumeration is 50% vs 38.6% overall (+11.4 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected come, 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 |
|---|---|---|---|---|
| c*m*m*i*o*f*n*n*i*r*.com | — | F | Aug 31, 2026 | |
| l*f*m*l*o*f*c*.com | — | F | Aug 19, 2026 | |
| v*c*t*o*l*f*e*s.com (WP 7.0.4) | — | F | Aug 17, 2026 | |
| c*m*o*m*d*a.pl (WP 6.5.8) | — | F | Aug 3, 2026 |
Page 1 of 1