Security snapshot
Across 20 appyn-17 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 usernames35%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS95%vs 96.3% avg
What stands out
TLDWP currently associates 20 indexed WordPress sites with appyn-17, 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 35% vs 38.6% overall (-3.6 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); HTTPS adoption is 95% vs 96.3% overall (-1.3 pp).
These are observational associations among sites where TLDWP detected appyn-17, 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*k*m*.com | 2.0.17· 100% conf. | F | Sep 10, 2026 | |
| a*k*a*e*.c*m.pk | 2.0.17· 100% conf. | F | Sep 9, 2026 | |
| p*3*3.c*m.pk | — | F | Sep 7, 2026 | |
| f*y*3*.c*m.pk | — | F | Sep 7, 2026 | |
| 3*5*e*a*.c*m.pk | — | F | Sep 2, 2026 | |
| n*7*7.pk | — | F | Sep 1, 2026 | |
| a*k*l*y*n*.c*m.pk | — | F | Aug 28, 2026 | |
| t*t*5*.c*m.pk | — | F | Aug 28, 2026 | |
| b*5*o*l*n*.c*m.pk | — | F | Aug 27, 2026 | |
| g*m*o*y.com | — | F | Aug 27, 2026 | |
| x*z*p*.org | — | F | Aug 24, 2026 | |
| p*r*l*t.c*m.pk | — | F | Aug 15, 2026 | |
| a*p*a*k.c*m.pk | — | F | Aug 9, 2026 | |
| a*c*r*.c*m.pk | — | F | Aug 6, 2026 | |
| a*k*a*e*.c*m.pk | — | F | Aug 4, 2026 | |
| g*t*p*.c*m.pk | — | F | Aug 4, 2026 | |
| p*9*9.pro | — | F | Aug 2, 2026 | |
| g*m*s*k*.c*m.pk | — | F | Aug 1, 2026 | |
| p*k*u*e*g*m*.com | — | F | Jul 31, 2026 | |
| a*k*i*i*.net | — | F | Jul 29, 2026 |
Page 1 of 1