WordPress maintenance or security needs? Reach out!
TLDWP

Theme: photothemeresponsive (Used by 40 domains)

Security snapshot

Across 40 photothemeresponsive 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 usernames3%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg

What stands out

TLDWP currently associates 40 indexed WordPress sites with photothemeresponsive, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 2.5% versus 38.6% overall (-36.1 percentage points).

Header-grade F is 100% vs 82.6% overall (+17.4 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).

These are observational associations among sites where TLDWP detected photothemeresponsive, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.

Where these sites live — top 1 domain endings
.com 40

photothemeresponsive Premium / Custom

This theme is not available on WordPress.org. It may be a premium theme, a custom theme, or a theme from a third-party marketplace.

DomainVersionExposuresHeadersLast Checked
t*k*s*r*o*a*.com (WP 3.4.2) 2.0· 100% conf. F Sep 10, 2026
t*k*d*.com (WP 3.4.2) 2.0· 100% conf. F Sep 10, 2026
t*u*a*a*k*n*o*.com (WP 3.4.2) 2.0· 100% conf. F Sep 9, 2026
f*n*n*k*.com (WP 3.4.2) 2.0· 100% conf. F Sep 9, 2026
t*i*-*a*o*.com (WP 3.4.2) F Sep 6, 2026
y*s*0*7.com (WP 3.4.2) F Sep 6, 2026
b*n*e*r*1*.com (WP 3.4.2) F Sep 5, 2026
d*n*i*o*g.com (WP 3.4.2) F Sep 5, 2026
d*i*i*n*k*i.com (WP 3.4.2) F Sep 5, 2026
h*y*b*s*-*o*.com (WP 3.4.2) F Sep 3, 2026
h*r*k*-*.com (WP 3.4.2) F Sep 1, 2026
n*w*y*u*j*n.com (WP 3.4.2) F Aug 30, 2026
t*k*r*-*.com (WP 3.4.2) F Aug 29, 2026
n*k*-*a*e*a*u.com (WP 3.4.2) F Aug 29, 2026
8*8*u*u*e*s*.com (WP 3.4.2) F Aug 27, 2026
e*m*s*o*.com (WP 3.4.2) F Aug 25, 2026
t*f*c*r*.com (WP 3.4.2) F Aug 25, 2026
g*i*t*h*.com (WP 3.4.2) F Aug 25, 2026
p*n*h*r*.com (WP 3.4.2) F Aug 24, 2026
g*n*t*e*a*t*n.com (WP 6.2.11) F Aug 23, 2026
a*n*e*o*o*a.com (WP 3.4.2) F Aug 22, 2026
s*p*r*o*h*k*n*.com (WP 3.4.2) F Aug 21, 2026
s*n*i*h*7*7.com (WP 3.4.2) F Aug 19, 2026
s*-*a*.com (WP 3.4.2) F Aug 18, 2026
w*s*o*u*k*s*i.com (WP 3.4.2) F Aug 17, 2026
p*n*a*o.com (WP 3.4.2) F Aug 16, 2026
w*k*z*s*.com (WP 3.4.2) F Aug 15, 2026
s*n*j*u.com (WP 3.4.2) F Aug 15, 2026
g*r*g*-*b*.com (WP 3.4.2) F Aug 1, 2026
b*c*c*.com (WP 3.4.2) F Aug 1, 2026
a*t*-*e*r.com (WP 3.4.2) F Jul 30, 2026
u*a*a*k*n*f*.com (WP 3.4.2) F Jul 30, 2026
r*u*i*o*i.com (WP 3.4.2) F Jul 27, 2026
k*o*b*k*.com (WP 3.4.2) F Jul 24, 2026
t*z*-*e*t*a*.com (WP 3.4.2) F Jul 24, 2026
a*t*o*n*i*d*a.com (WP 7.0.2) F Jul 24, 2026
r*r*g*r*o*t*.com F Jul 23, 2026
u*y*s*-*.com (WP 3.4.2) F Jul 21, 2026
e*o*h*n.com (WP 3.4.2) F Jul 21, 2026
f*-*.com (WP 3.4.2) F Jul 21, 2026