Security snapshot
Across 14 prettify-code-syntax WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 14 indexed WordPress sites with prettify-code-syntax, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 64.3% versus 38.5% overall (+25.8 percentage points).
Header-grade F is 71.4% vs 82.5% overall (-11.1 pp); Sensitive-file exposure is 7.1% vs 1.8% overall (+5.3 pp); HTTPS adoption is 92.9% vs 96.2% overall (-3.3 pp).
These are observational associations among sites where TLDWP detected prettify-code-syntax, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
Prettify Code Syntax
The main reason for the development of this plugin was the lack of options supporting the HTML5 recommendation, where the code snippets should be tagged with pre followed by code, and optionally a class starting with language- and then our language. You can use the plugin like this: // my code Also very important is that although this plugin loads different files depending on your configuration, it fully supports caching scripts (W3 Total Cache) to concatenate and compress all the css and js, so the impact in…
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| b*a*d*n*i*e.com (WP 7.1) | F | Sep 8, 2026 | |
| m*r*m*c*p*g*l.com (WP 6.3.10) | F | Sep 3, 2026 | |
| j*s*p*g*h*i*.com (WP 7.1) | F | Aug 31, 2026 | |
| j*q*a*r*.com (WP 4.7.29) | B | Aug 24, 2026 | |
| c*d*g*g*n*r*t*v*.com (WP 6.8.1) | F | Aug 23, 2026 | |
| e*s*m*i*7.com | F | Aug 20, 2026 | |
| h*x*d*i*e.jp | F | Aug 17, 2026 | |
| d*u*-*e*c*a*t*a*i.com | A | Aug 16, 2026 | |
| s*n*b*i.com (WP 7.0.4) | F | Aug 15, 2026 | |
| b*p*d*o*k.com (WP 7.0.2) | F | Aug 1, 2026 | |
| s*l*a*e*d*s*g*s.com | D | Jul 30, 2026 | |
| f*u*f*n*k*i*.com (WP 6.9.5) | F | Jul 28, 2026 | |
| k*s*i.net | F | Jul 21, 2026 | |
| t*a*.info (WP 6.8.6) | C | Jul 20, 2026 |