Security snapshot
Across 23 nocache-bfcache WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 23 indexed WordPress sites with nocache-bfcache, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 52.2% versus 82.5% overall (-30.3 percentage points).
Username enumeration is 21.7% vs 38.5% overall (-16.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); HTTPS adoption is 95.7% vs 96.2% overall (-0.5 pp).
These are observational associations among sites where TLDWP detected nocache-bfcache, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
Instant Back/Forward
This plugin was formerly called as “No-cache BFCache”, which admittedly was a poor jargony name and was too narrowly scoped. This plugin enables instant back/forward navigation via the browser’s bfcache. It does this by removing the no-store directive from the Cache-Control response header, which WordPress sends by default when nocache_headers() is called. This happens primarily when a user is logged in, but some plugins may send these “no-cache” headers such as on the Cart or Checkout pages for an e-commerce site.…
| Domain | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| d*r*t*d*w*a*o*h*r*o*l*d*e*m.com (WP 7.0.4) | — | A | Sep 7, 2026 | |
| k*m*b*r*.com | — | F | Sep 6, 2026 | |
| m*h*b*1.com | — | C | Sep 6, 2026 | |
| o*k*s*u*d*o*s.com | — | F | Sep 3, 2026 | |
| r*m*d*c*l*o*r*.com | — | D | Sep 2, 2026 | |
| o*t*c*s.c*.uk (WP 7.0.4) | — | A | Sep 2, 2026 | |
| s*o*y*a*l.com (WP 6.9.7) | — | F | Aug 29, 2026 | |
| b*t*r*o*-*m*g*s.com | — | B | Aug 24, 2026 | |
| g*o*o*i*s.com | — | C | Aug 23, 2026 | |
| t*c*z*i*a*e*.com | — | B | Aug 20, 2026 | |
| s*a*s*o*e.com (WP 7.0.4) | — | F | Aug 16, 2026 | |
| d*o*l*n*i*i.com | — | F | Aug 15, 2026 | |
| s*o*t*d*a*.hu (WP 7.0.4) | — | F | Aug 14, 2026 | |
| i*f*t.org | — | F | Jul 30, 2026 | |
| t*c*z.com | — | A | Jul 29, 2026 | |
| c*m*u*r*h*a*t*.com | — | B | Jul 26, 2026 | |
| g*a*i*y*a*h.com | — | B | Jul 26, 2026 | |
| g*a*i*y*i*e*t*r*.com | — | F | Jul 26, 2026 | |
| 9*j*w*l*r*.com | — | F | Jul 25, 2026 | |
| r*y*l*y*j*w*l*r*.com | — | F | Jul 25, 2026 | |
| m*y*o*d*j*a.c*m.tw (WP 7.0) | — | F | Jul 25, 2026 | |
| r*t*i*.es (WP 6.9.5) | — | B | Jul 24, 2026 | |
| g*e*c*l.com | — | F | Jul 19, 2026 |