WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: nearby-locations (Used by 20 domains)

Security snapshot

Across 20 nearby-locations WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 45% Grade B 0% Grade C 0% Grade D 15% Grade F 40%
Fail the header check (F)40%vs 82.5% avg
Leak usernames15%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg

What stands out

TLDWP currently associates 20 indexed WordPress sites with nearby-locations, 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 15% vs 38.5% overall (-23.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 nearby-locations, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.

Nearby Locations

👤 aaronfrey

Add the ability to add locations to a map, based on category, in relation to a single location.

Domain Exposures Headers Last Checked
t*i*l*u*-*i*l*g*.com (WP 7.0.4) F Sep 6, 2026
r*n*l*n*e*p*r*.com A Sep 5, 2026
r*n*g*o*e*t*l*a*.com A Sep 5, 2026
r*n*c*r*y*e*a*d*n*.com A Sep 5, 2026
t*a*l*a*s*l*o*c*e*k.com (WP 7.0.4) D Sep 3, 2026
l*v*o*d*r*h*r*.com A Aug 28, 2026
l*v*e*t*n*q*a*e.com A Aug 28, 2026
l*v*c*a*h*m*a*d*n*.com A Aug 28, 2026
l*v*b*r*a*w*o*s.com A Aug 28, 2026
l*v*a*w*o*g*t*.com A Aug 28, 2026
1*5*i*l.com F Aug 21, 2026
v*n*a*e*o*n*h*u*t*n.com (WP 7.0.4) F Aug 18, 2026
c*n*r*a*s*l*e*s*r*n*a*t*.com A Aug 18, 2026
b*a*t*.com F Jul 31, 2026
h*c*2.com F Jul 30, 2026
l*p*a*a*o.com F Jul 28, 2026
a*p*n*i*l*g*p*r*.com F Jul 26, 2026
t*e*r*i*s*p*r*m*n*s.com (WP 7.0.2) D Jul 24, 2026
r*c*p*s.com F Jul 20, 2026
r*v*r*a*s*a*a*.com (WP 7.0.2) D Jul 19, 2026