Security snapshot
Across 7 azzle-1 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 usernames29%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 7 indexed WordPress sites with azzle-1, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.5% overall (+17.5 percentage points).
Username enumeration is 28.6% vs 38.5% overall (-9.9 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 azzle-1, 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 |
|---|---|---|---|---|
| i*r*w.software (WP 7.1) | — | F | Sep 5, 2026 | |
| r*a*l*f*.com (WP 6.8.8) | — | F | Sep 3, 2026 | |
| e*p*o*z*.com (WP 6.9.7) | — | F | Aug 28, 2026 | |
| m*r*c*r*.software (WP 7.0.3) | — | F | Aug 7, 2026 | |
| m*r*c*r*.net (WP 7.0.2) | — | F | Aug 4, 2026 | |
| p*i*m*.com | — | F | Jul 31, 2026 | |
| i*r*w*s*f*w*r*.com (WP 7.0.2) | — | F | Jul 23, 2026 |
Page 1 of 1