WordPress plugin intelligence profile

Security Headers

Plug-in to ease the setting of TLS headers for HSTS and similar

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 5.1
Current version1.1
WordPress coverageTested up to WordPress 5.1
Minimum stackWP 3.8.1 · PHP 5.6
Directory statusactive
Last directory update26 Feb 20197y ago
Active installations3K+Adoption metric — not a quality score
WordPress.org rating5.0 / 5 from 8 ratings
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Security Headers version 1.1 as active, updated 7y ago and tested up to WordPress 5.1.

Overview

About this plugin

TLS is growing in complexity. Server Name Indication (SNI) now means HTTPS sites may be on shared IP addresses, or otherwise restricted. htaccess file.

This plug-in exposes controls for:

  • HSTS (Strict-Transport-Security)
  • HPKP (Public-Key-Pins)
  • Disabling content sniffing (X-Content-Type-Options)
  • XSS protection (X-XSS-Protection)
  • Clickjacking mitigation (X-Frame-Options in main site)
  • Expect-CT

HSTS is used to ensure that future connections to a website always use TLS, and disallowing bypass of certificate warnings for the site.

HPKP is used if you don’t want to rely solely on the Certificate Authority trust model for certificate issuance.

Disabling content sniffing is mostly of interest for sites that allow users to upload files of specific types, but that browsers might be silly enough to interpret of some other type, thus allowing unexpected attacks.

XSS protection re-enables XSS protection for the site, if the user has disabled it previously, and sets the “block” option so that attacks are not silently ignored.

Clickjacking protection is usually only relevant when someone is logged in but users requested it, presumably they have rich content outside of WordPress authentication they wish to protect.

Expect-CT is used to ensure Certificate Transparency is configured correctly.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • hsts
  • https
  • nosniff
  • tls
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 5.1

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 5.1.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to5.1
Minimum requirementsWordPress 3.8.1 · PHP 5.6
Update activity26 Feb 20197y ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.