Security snapshot
Across 5 inplant 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 usernames80%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 inplant, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 80% versus 38.5% overall (+41.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 inplant, 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 |
|---|---|---|---|---|
| x*-*p*q*8*y*4*3*7*e*2*a.com (WP 4.9.8) | — | F | Sep 3, 2026 | |
| x*-*e*k*d*b*d*b*7*2*d*h*a.com (WP 4.9.8) | — | F | Sep 2, 2026 | |
| t*b*-*a*t*.com (WP 4.7.35) | — | F | Aug 25, 2026 | |
| i*p*a*t*r*i*i*g*a*u*a*.in | — | F | Aug 22, 2026 | |
| i*p*a*t*k*c*i*o*i*e*.com (WP 4.9.8) | — | F | Aug 18, 2026 |
Page 1 of 1