Better Headers

Ownership

Held by bettersecurity throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.

Full observed history, including every field transition

Committing accounts

Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.

This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.

Adoption

How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.

Very early-stage: 80+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.

3 downloads a day over the last 7 days, rising 100% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.

Install band rose to 80+ on 22 Oct 2026, from 70+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.

Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.

Unchanged throughout: ratings total (1) · version (2.1) · support threads (0) · threads resolved (0)

91 days of observation, most recent 14 shown.

Maintenance

When it was last released, and how far its declared compatibility has drifted from current WordPress.

History

Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.

Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.

1. 21 Oct 202618 days ago
   Install band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
2. 02 Aug 20263 months ago
   Install band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
3. 02 Aug 20263 months ago
   First observed by PluginsPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
4. 22 Mar 20268 months ago
   Dormancy threshold crossed540 days since the last release (2024-09-28). Dormancy is a maintenance observation, not a judgement about the owner.
5. 28 Sep 20242 years ago
   Version 2.1 released
6. 09 Dec 20196.5 years ago
   Version 1.6 releasedfrom the release logCommitted by bettersecurity.
7. 13 Jun 20197 years ago
   Version 1.5 releasedfrom the release logCommitted by riklewis.
8. 10 Jun 20197 years ago
   Version 1.3 releasedfrom the release logCommitted by riklewis.
9. 10 Jun 20197 years ago
   Version 1.4 releasedfrom the release logCommitted by riklewis.
10. 11 Mar 20197.5 years ago
    Version 1.0 releasedfrom the release logCommitted by riklewis.
11. 11 Mar 20197.5 years ago
    Version 1.1 releasedfrom the release logCommitted by riklewis.
12. 11 Mar 20197.5 years ago
    Version 1.2 releasedfrom the release logCommitted by riklewis.
13. 09 Mar 20197.5 years ago
    Added to the WordPress.org directoryReported by the plugin API as the date this plugin was added.

What we know, and what we don’t

Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.

Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see

Similar plugins

This plugin has not been updated in a long time. These carry the same tags and describe themselves in the same terms, so they are a starting point for a replacement, not a recommendation. Check them yourself.

WP Hide & Security Enhancer

Protect your website by concealing vulnerable WordPress traces, plugins, themes, login/admin url. 2FA, Captcha, Firewall, Security Headers etc.

50,000+ installs4.3★ (275)updated 23 Sep 2026

headerssecurity

Headers Security Advanced & HSTS WP

Best all-in-one WordPress security plugin, uses HTTP & HSTS response headers to avoid vulnerabilities: XSS, injection, clickjacking. Force HTTP/HTTPS.

90,000+ installs4.8★ (80)updated 30 Oct 2026

headers

Host Header Injection Fix

Sets custom headers for WP notification emails. Also fixes a security issue with WP versions < 5.5.

400+ installs5.0★ (6)updated 18 Jul 2026

headerssecurity

Security Hardener

Hardens WordPress with secure headers, login protection, user enumeration blocking, rate limiting, and a built-in security checklist.

200+ installsupdated 28 Oct 2026

headerssecurity

HT Security

Complete Security Suite: Security Headers, CVE Detection, Core Integrity, Login Alerts, Plugin Update Management, Force Cron, and Maintenance Mode.

100+ installs5.0★ (1)updated 10 Aug 2026

headerssecurity

EssentialHeaders

Adds the essential HTTP security headers WordPress leaves out—on every public site response.

40+ installsupdated 28 Aug 2026

headerssecurity

Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.

Reach out about this record

Corrections, missing context, or anything else about Better Headers: a person reads every submission, and corrections get a reply within 5 business days.