Plugin profile · observed daily since 16 Aug 2026
EssentialHeaders
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Alex Hedström throughout, with no change of ownership observed since daily tracking began on 16 Aug 2026.
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: 10+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
8 downloads a day averaged over 12 days. WordPress.org reports a running download total; the gap between two days is that day’s downloads. Unlike the install figure it is exact and has no ceiling, so it shows movement the rounded band cannot. Too few days so far to say whether it is rising or falling.
Install band fell to 10+ on 18 Aug 2026, from 20+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.
Daily record
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.
| Field | 16 Aug | 17 Aug | 18 Aug | 19 Aug | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 34 | 12 | 11 | 11 | 0 | 0 | 11 | 0 | 0 | 11 | 0 | 0 |
| Active installs | 10+ | 20+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ |
| Version | 1.0.0 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.2 |
Unchanged throughout: ratings total (0) · support threads (0) · threads resolved (0)
13 days of observation.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Is anyone still maintaining this?
- Last released 28 Aug 2026, 1 days ago.
- Declares compatibility with WordPress 7.1, which is current.
- The same account maintains 3 other plugins, 3 of which were updated in the last 90 days. the account is active.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
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.
- 28 Aug 2026yesterdayVersion 1.0.2 released
- 17 Aug 202612 days agoInstall band moved to 20+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 16 Aug 202613 days agoVersion 1.0.1 released
- 16 Aug 202613 days agoInstall band moved to 10+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 16 Aug 202613 days agoFirst observed by PluginPediaDaily 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.
- 14 Aug 202615 days agoVersion 1.0.0 released
- 14 Aug 202615 days agoAdded 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.
What we know
- It has been held by Alex Hedström for all 13 days we have observed it.
- It was last released yesterday (28 Aug 2026).
- Its author declares it tested up to WordPress 7.1, which is current.
- WordPress.org reports 10+ active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
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
Plugins that share this one’s tags and talk about the same things in their own descriptions. Distinctive tags count for far more than broad ones. Sharing hover means something, sharing woocommerce does not, and a plugin that never mentions the subject matter is left out however its author tagged it. Among close matches, more widely installed plugins are listed first. This is a grouping rather than a ranking of quality.
Best all-in-one WordPress security plugin, uses HTTP & HSTS response headers to avoid vulnerabilities: XSS, injection, clickjacking. Force HTTP/HTTPS.
Enhance your WordPress site security with HTTP security headers and improve performance with smart caching. Works with all hosting providers.
Configure various security-related HTTP headers, including CSP, XSS, Referrer Policy and more.
Protect your website by concealing vulnerable WordPress traces, plugins, themes, login/admin url. 2FA, Captcha, Firewall, Security Headers etc.
Configure core HTTP security headers for your WordPress site in a few clicks.
🛡️ Enterprise-grade WordPress security made simple. Implement military-standard HTTP security headers with zero technical knowledge required.
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 EssentialHeaders: a person reads every submission, and corrections get a reply within 5 business days.