WordPress plugin
Security Headers
Plug-in to ease the setting of TLS headers for HSTS and similar
- Active installs
- 3K+
- Rating
- 5.0 / 5
- Version
- 1.1
- Last updated
- Feb 26, 2019
- Tested up to
- WordPress 5.1.28
- Requires
- WP 3.8.1 · PHP 5.6
Health check
Is Security Headers safe to rely on?
Our reading of the public WordPress.org data: maintenance, compatibility, ratings and support.
No update in over a year
Last updated on February 26, 2019. It may not be compatible with current WordPress or PHP, and unfixed issues are a security risk.
Not yet tested with the latest WordPress
Tested up to WordPress 5.1.28. It often still works, but check on staging first.
Few ratings so far
Only 8 ratings on WordPress.org, so the average is not yet a reliable signal.
Requires PHP 5.6 or newer
Check your hosting PHP version before installing. Modern PHP is faster and receives security fixes.
Rank tracker
Where Security Headers ranks in WordPress.org search
Its position in WordPress.org plugin search for its tags and name, refreshed weekly so you can see how its visibility changes.
| Keyword | Position | Change | Trend | Current #1 |
|---|---|---|---|---|
| hsts | ||||
| https | ||||
| nosniff | ||||
| tls | ||||
| security headers |
Checked against the top 100 WordPress.org search results.
Overview
What Security Headers does
TLS is growing in complexity. Server Name Indication (SNI) now means HTTPS sites may be on shared IP addresses, or otherwise restricted. For these servers it is handy to be able to set desired HTTP headers without access to the web servers configuration or using .htaccess file.
This plug-in exposes controls for:
Disabling content sniffing (X-Content-Type-Options)
Clickjacking mitigation (X-Frame-Options in main site)
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.
Description from the author's listing. Read the full listing on WordPress.org
FAQ
Security Headers: questions and answers
What is Security Headers?
Security Headers is a WordPress plugin by SimonRWaters. Plug-in to ease the setting of TLS headers for HSTS and similar
Is Security Headers free?
Security Headers is listed in the WordPress.org plugin directory, so the version there is free to download and use. Some authors also sell paid add-ons or a premium edition with more features and support.
How many websites use Security Headers?
WordPress.org reports 3K+ active installations of Security Headers. That figure counts sites running the WordPress.org version and is rounded down by WordPress.org.
Is Security Headers still maintained?
Security Headers was last updated on February 26, 2019. The current version is 1.1. Check the changelog on WordPress.org and test updates on a staging site before applying them to a live site.
What does Security Headers require?
Security Headers requires WordPress 3.8.1 or newer and PHP 5.6 or newer. It has been tested up to WordPress 5.1.28.
Can Codefreex set up or customize Security Headers?
Yes. Codefreex installs, configures and customizes WordPress plugins including Security Headers, fixes conflicts and performance problems, and builds custom features when a plugin does not do exactly what you need. Send your site URL for a free review.
Free expert review
Need Security Headers set up, customized or fixed?
Tell us about your site and what you need this plugin to do. A senior WordPress developer replies within one business day with a plan and a quote.