Security snapshot
Across 7 nofollow-case-by-case WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 7 indexed WordPress sites with nofollow-case-by-case, equivalent to 0% of the current WordPress dataset.
The largest measured difference is HTTPS adoption: 71.4% versus 96.2% overall (-24.8 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.5 pp); Username enumeration is 42.9% vs 38.5% overall (+4.4 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected nofollow-case-by-case, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
Nofollow Case by Case
For unmodified links Nofollow Case by Case works like a (do)follow plugin for WordPress. It simply removes rel=”nofollow” from your comment links. Whenever you get the feeling that one of your comment links might be able to harm your own website reputation, if you think about SEO and found a link that looks a bit like spam but should not be deleted, you can replace nofollow to every single comment link at any time. If…
| Domain | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| h*g*f*y*4.com (WP 4.0.1) | — | F | Sep 8, 2026 | |
| z*e*e*i*.com (WP 7.0.4) | — | F | Sep 3, 2026 | |
| n*s*n*o*r*k*u*-*u*d*.com | — | F | Aug 27, 2026 | |
| p*a*e*a*k*n*.c*.uk (WP 7.0.4) | — | F | Aug 24, 2026 | |
| j*s*a*d*a*e*.dk (WP 5.1.22) | — | F | Aug 1, 2026 | |
| a*e*u*z*o*l*o*.com (WP 7.0.2) | — | F | Jul 31, 2026 | |
| p*i*a*a*a*e*r*c*m.com (WP 5.7.15) | — | F | Jul 30, 2026 |