Security snapshot
Across 4 wpjm-auto-location-2 WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 25%
Grade F 75%
Fail the header check (F)75%vs 82.5% avg
Leak usernames75%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 4 indexed WordPress sites with wpjm-auto-location-2, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 75% versus 38.5% overall (+36.5 percentage points).
Header-grade F is 75% vs 82.5% overall (-7.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 wpjm-auto-location-2, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| g*p*u*e*p*e*s.jobs (WP 6.6.7) | F | Aug 16, 2026 | |
| m*m*r.id (WP 6.7.1) | D | Aug 2, 2026 | |
| s*g*l*.com | F | Jul 29, 2026 | |
| n*r*h*e*t*o*k*.ca (WP 7.0.2) | F | Jul 25, 2026 |
Page 1 of 1