Security snapshot
Across 3 ristorante-child 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 usernames33%vs 38.6% avg
Expose a sensitive file33.3%vs 1.8% avg
Use HTTPS67%vs 96.3% avg
What stands out
TLDWP currently associates 3 indexed WordPress sites with ristorante-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is sensitive-file exposure: 33.3% versus 1.8% overall (+31.5 percentage points).
HTTPS adoption is 66.7% vs 96.3% overall (-29.6 pp); Header-grade F is 100% vs 82.6% overall (+17.4 pp); Username enumeration is 33.3% vs 38.6% overall (-5.3 pp).
These are observational associations among sites where TLDWP detected ristorante-child, 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 |
|---|---|---|---|---|
| p*z*a*l*c*o*i.com (WP 6.9) | 1.0.0· 100% conf. | F | Sep 10, 2026 | |
| a*e*e*o*t*a.pl (WP 6.1.10) | — | — | Sep 9, 2026 | |
| a*b*r*e*l*g*b*r.com (WP 6.7.5) | — | F | Jul 29, 2026 |
Page 1 of 1