WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: photospace-responsive (Used by 216 domains)

Security snapshot

Across 216 photospace-responsive WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 4% Grade F 95%
Fail the header check (F)95%vs 82.5% avg
Leak usernames48%vs 38.5% avg
Expose a sensitive file2.8%vs 1.8% avg
Use HTTPS94%vs 96.2% avg

What stands out

TLDWP currently associates 216 indexed WordPress sites with photospace-responsive, equivalent to 0% of the current WordPress dataset.

The largest measured difference is header-grade F: 95.4% versus 82.5% overall (+12.9 percentage points).

Username enumeration is 48.1% vs 38.5% overall (+9.6 pp); HTTPS adoption is 93.5% vs 96.2% overall (-2.7 pp); Sensitive-file exposure is 2.8% vs 1.8% overall (+1 pp).

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

Infrastructure patterns

Infrastructure detected alongside photospace-responsive. Percentages are within sites where that specific signal was detectable; the baseline compares the same signal across detected WordPress sites overall.

Co-occurrence describes technologies observed on the same sites. Detection coverage varies by signal, and an association does not imply that one technology caused or selected another.

Photospace Responsive Gallery

Based on the Galleriffic gallery, Photospace takes advantage of the built in gallery features of WordPress. Then simply use the WordPress admin to create a gallery and insert it in the page. You may need to adjust the size of the gallery to suit your theme in the settings. Since WordPress 5 you need to embed the gallery using the classic editor. Make a note of your settings as with the last major update, you will need re-save your settings.…

Domain Exposures Headers Last Checked
h*o*i*h*-*a*k*u.com (WP 6.3.10) F Sep 9, 2026
c*m*t*-*r*e*n*s*h*n*b*l*.fr (WP 7.1) F Sep 9, 2026
f*s*k*r*y*.com (WP 7.1) F Sep 9, 2026
m*k*k.cc (WP 5.7.17) F Sep 9, 2026
e*v*i*s*c.com (WP 7.0.4) F Sep 9, 2026
r*c*a*d*o*o*.com (WP 7.1) F Sep 8, 2026
e*p*s*d*c.com (WP 6.5.10) F Sep 8, 2026
h*g*s*i*s*o*i.com (WP 7.1) F Sep 8, 2026
o*a*m*r*u*s*h*t*g*a*h*.com (WP 5.7.1) F Sep 8, 2026
e*r*p*o*e*t*.cz (WP 5.8.2) F Sep 8, 2026
h*b*k*-*i*s*i*y*.com (WP 5.4.21) F Sep 7, 2026
o*i*i*s*e*c*r*o*e*.com (WP 4.6.29) F Sep 7, 2026
k*r*n*l*r*s*u*i*.com (WP 4.9.18) F Sep 7, 2026
f*f*.org (WP 5.9.16) D Sep 7, 2026
y*s*i*a*a*o*o.com (WP 6.0.12) F Sep 7, 2026
a*l*i*m*h*f*i*l*.c*.uk D Sep 7, 2026
d*s*g*i*t*i*i*n*.com (WP 6.8.8) F Sep 6, 2026
y*g*v*o*a.com (WP 6.4.10) F Sep 6, 2026
k*e*t*u*1*2.com F Sep 6, 2026
t*e*m*k*n*e*d*s*g*.com (WP 4.3) F Sep 6, 2026
e*e*-*i*e.com (WP 4.1) F Sep 6, 2026
d*n*e*r*o.com (WP 7.0.4) F Sep 6, 2026
d*l*s*n*i*u*r*d*o.com (WP 6.9.7) F Sep 5, 2026
c*m*o*r*n*e*o*i*i*s.c*m.br F Sep 5, 2026
s*o*y*i*e*l*v*n*e*.com (WP 6.9.7) D Sep 5, 2026
d*i*o*j*u*k*n.com F Sep 5, 2026
k*g*f*k*s*i*n.com (WP 5.4.21) F Sep 5, 2026
y*n*k*c*i.com (WP 5.3.23) F Sep 5, 2026
k*k*d*k*r*.com F Sep 4, 2026
d*p*l*a.com (WP 7.0.4) F Sep 4, 2026
j*s*n*a*a.com F Sep 3, 2026
x*-*v*k*1*x*s*6*y*1*.com (WP 7.1) F Sep 3, 2026
e*p*r*n*a*s*l*n.com (WP 5.1.19) F Sep 3, 2026
c*z*i*a.com F Sep 3, 2026
h*t*v*1*.com (WP 6.1.12) F Sep 2, 2026
i*a*o*l*n*s*s*e*s.c*.uk (WP 3.5.1) F Sep 2, 2026
t*s*i*k*n*0*0.com F Sep 1, 2026
t*r*n*o*r*u*a*u.com (WP 7.0.3) F Sep 1, 2026
r*k*e*-*n*.com (WP 6.2.11) F Aug 31, 2026
m*r*a*a*e*t*h*p*.com (WP 4.9.26) F Aug 31, 2026
m*r*a*m*l*e*.com (WP 7.0.4) F Aug 31, 2026
y*u*-*r*h*.com F Aug 30, 2026
n*w*i*i*i.com F Aug 30, 2026
r*f*n.ca F Aug 30, 2026
i*t*e*u*t*.jp F Aug 29, 2026
a*-*a*i.com (WP 6.8.8) F Aug 29, 2026
t*o*d*l*a*k*h*l*.de (WP 6.7.2) F Aug 29, 2026
c*e*d*n*e.com F Aug 29, 2026
c*e*a*t*a*d*a*c*.com F Aug 29, 2026
d*y*o*c*p*s.com F Aug 28, 2026
s*r*e*l*m*t*r*p*r*.ch F Aug 28, 2026
b*t*n*c.c*.uk F Aug 28, 2026
e*u*h*y*.jp (WP 7.1) F Aug 28, 2026
c*a*t*a*t*w*r*d.com F Aug 28, 2026
t*o*i*e*o*e*.org F Aug 27, 2026
j*n*i*e*g*r*i*u*s.com F Aug 27, 2026
s*i*s*k*n*a*a*h*.com (WP 6.6.7) F Aug 27, 2026
m*k*b*s*i*m*i*a.com (WP 7.1) F Aug 27, 2026
t*k*s*i*s*g*.com (WP 7.0.4) F Aug 26, 2026
s*i*o*i*k*i*a*.com (WP 7.1) F Aug 26, 2026
6*s*l*n.com F Aug 26, 2026
d*v*s*r*n*g*t*e*l*b*i*t*u*i*t*k.de F Aug 26, 2026
l*n*a*h*m*s*n*u*i*.com F Aug 26, 2026
5*0*u*.com (WP 5.9.16) F Aug 26, 2026
e*p*l*d*a*e*l*n*.com (WP 7.1) F Aug 26, 2026
g*i*e*-*u*m*n*b*a*c.com (WP 6.5.2) F Aug 26, 2026
p*e*f*l*.us (WP 6.1.10) F Aug 25, 2026
4*1*u*d*t*m*a*i*e*c*.com (WP 7.1) F Aug 25, 2026
4*1*u*d*t*m*a*i.com (WP 7.1) F Aug 25, 2026
p*u*m*t*i*u.ca (WP 7.0.4) F Aug 25, 2026
p*l*t*s*u*c*i*n*l.es (WP 5.4.21) F Aug 25, 2026
l*g*t*h.com (WP 5.7.17) F Aug 25, 2026
n*d*n*b*u*h*o*.com F Aug 25, 2026
a*t*z*m*n*.jp (WP 7.0.4) F Aug 24, 2026
s*m*h*n*-*a*l*t.com (WP 6.0.2) F Aug 24, 2026
d*l*u*a*o*s.com (WP 7.1) F Aug 24, 2026
a*i*a*d*n*a*.com F Aug 24, 2026
w*s*i*p*t*h*r*r*.com (WP 7.1) F Aug 23, 2026
s*i*i*h*l*.us (WP 5.3.23) F Aug 23, 2026
c*o*y*t.com F Aug 23, 2026
p*o*i*s*s*i*r*.com F Aug 23, 2026
2*t*-*o*k*.com F Aug 22, 2026
c*a*t*r*o*i*t.com F Aug 22, 2026
e*h*t*e*t*r*u*t*a*e.com F Aug 21, 2026
s*o*y*i*e*l*v*n*e*.c*m.au (WP 6.9.7) D Aug 21, 2026
e*i*a*e*f*r*i*g*r*s.com (WP 5.9.16) F Aug 21, 2026
b*a*s*d*s*g*.com F Aug 21, 2026
i*a*i*n*r*g*i*e*.com (WP 4.9.26) F Aug 21, 2026
h*t*l*b*h*m*.fr (WP 6.0.14) F Aug 20, 2026
l*i*h*a*g*d*.com F Aug 20, 2026
o*r*v*o*e*u*p*r*u*i*e.cz (WP 5.0.22) F Aug 20, 2026
g*l*e*y*n*h*m*r*h.com (WP 7.0.4) F Aug 19, 2026
i*d*a*l*b*a*a*.com (WP 6.3.10) F Aug 19, 2026
m*r*e*g*a*i*.com F Aug 19, 2026
g*r*o*d*v*d*o*m*d*r*a*t.com C Aug 19, 2026
d*a*f*i*a*f*.com (WP 5.4.21) F Aug 18, 2026
c*i*f*o*e*a*d*n*.com (WP 7.0.4) F Aug 18, 2026
p*t*a*o*u*o*a.com (WP 6.9.7) F Aug 17, 2026
s*i*a*t*i*k*k*i.com (WP 6.8.8) F Aug 17, 2026
d*n*u*n*l*c*c*r*c*n*r*.com (WP 7.0.4) F Aug 17, 2026