Security snapshot
Across 4 arise-twitter-override 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 arise-twitter-override, 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 arise-twitter-override, 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 |
|---|---|---|---|---|
| a*t*e*a*y*n*e*n*t*o*a*.org (WP 7.0.4) | — | F | Sep 7, 2026 | |
| a*i*e*l*i*n*e*n*t*t*t*.org (WP 7.0.4) | — | F | Sep 7, 2026 | |
| a*i*e*l*i*n*e.org (WP 7.0.4) | — | F | Sep 5, 2026 | |
| c*i*i*a*m*m*r*i*t*g*a*i*n.com (WP 7.0.4) | — | F | Sep 1, 2026 |
Page 1 of 1