Security snapshot
Across 5 cruiseappy-json WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 60%
Grade D 0%
Grade F 40%
Fail the header check (F)40%vs 82.5% avg
Leak usernames20%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 cruiseappy-json, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 40% versus 82.5% overall (-42.5 percentage points).
Username enumeration is 20% vs 38.5% overall (-18.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 cruiseappy-json, 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 |
|---|---|---|---|---|
| v*s*o*c*u*s*.c*.uk | — | F | Sep 8, 2026 | |
| c*u*s*u*i*u*.com | — | C | Aug 30, 2026 | |
| c*u*s*3*5.com | — | C | Aug 30, 2026 | |
| v*s*o*c*u*s*.com | — | F | Jul 27, 2026 | |
| c*u*s*p*r*d*s*.ie | — | C | Jul 21, 2026 |
Page 1 of 1