Security snapshot
Across 4 aruxcont-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 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 aruxcont-child, 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 aruxcont-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*a*s*n*o*s*l*i*g.ie (WP 6.3.5) | — | F | Aug 16, 2026 | |
| a*r*c*.be (WP 7.0.2) | — | F | Aug 4, 2026 | |
| i*o*s*u*i*r*b*a.com (WP 6.2.9) | — | F | Jul 29, 2026 | |
| o*s*r*a*o*r*-*a*i*e*o*c*t*n*e.fr (WP 6.9.4) | — | F | Jul 22, 2026 |
Page 1 of 1