Title: EssentialHeaders
Author: Alex Hedström
Published: <strong>14.08.2026</strong>
Last modified: 28.08.2026

---

Шукати плагіни

![](https://ps.w.org/essentialheaders/assets/banner-772x250.png?rev=3646718)

![](https://ps.w.org/essentialheaders/assets/icon-256x256.png?rev=3646718)

# EssentialHeaders

 Від автора [Alex Hedström](https://profiles.wordpress.org/alexhedstrom/)

[Завантажити](https://downloads.wordpress.org/plugin/essentialheaders.1.0.2.zip)

 * [Деталі](https://uk.wordpress.org/plugins/essentialheaders/#description)
 * [Відгуки](https://uk.wordpress.org/plugins/essentialheaders/#reviews)
 *  [Встановлення](https://uk.wordpress.org/plugins/essentialheaders/#installation)
 * [Розробка](https://uk.wordpress.org/plugins/essentialheaders/#developers)

 [Підтримка](https://wordpress.org/support/plugin/essentialheaders/)

## Опис

EssentialHeaders is a focused WordPress plugin that attaches the HTTP security headers
browsers expect, so protection is not left to chance or buried in server config.

Under Settings  EssentialHeaders you get three tabs:

 * Headers — overview of which headers are enabled and will be sent
 * Settings — toggles and editable values for each header
 * About — plugin info

Headers covered:

 * Content-Security-Policy (CSP)
 * Strict-Transport-Security (HSTS)
 * X-Frame-Options
 * X-Content-Type-Options
 * Referrer-Policy
 * Permissions-Policy
 * X-Powered-By (remove it or replace its value)

Safer headers are enabled with sensible defaults. CSP starts off with a strict baseline,
so you can test and allow only the sources your site needs before enabling it. Headers
apply to public site responses (pages, feeds, and the login screen)—not wp-admin,
AJAX, REST, GraphQL, or XML-RPC. HSTS is only sent over HTTPS. Default HSTS uses
max-age only; add includeSubDomains yourself when every subdomain is ready.

## Встановлення

 1. Upload the `essentialheaders` folder to the `/wp-content/plugins/` directory.
 2. Activate the plugin through the Plugins menu in WordPress.
 3. Open Settings  EssentialHeaders to review and configure headers.

## Часті питання

### Will this break my site?

The default set is conservative. Content-Security-Policy is off by default because
a strict CSP can block scripts or styles your theme needs. Enable CSP when you are
ready to tune it.

### Does HSTS work on HTTP?

No. Strict-Transport-Security is only sent when the visitor reaches the site over
HTTPS.

### Does the login screen get these headers?

Yes. The login screen is treated as a public response. wp-admin, AJAX, REST, GraphQL,
and XML-RPC are excluded, so dashboards and APIs are not broken by a strict CSP.

### Does this change site content?

No. The plugin only stores its own options and manages HTTP response headers on 
public responses.

### Can X-Powered-By always be removed?

EssentialHeaders removes PHP- and WordPress-managed instances at the latest applicable
WordPress header hook. Another callback running afterward, a reverse proxy, or a
web server can add the header again; remove it at that layer as well.

## Відгуки

Для цього плагіна немає відгуків.

## Учасники та розробники

“EssentialHeaders” — проект з відкритим вихідним кодом. В розвиток плагіну внесли
свій вклад наступні учасники:

Учасники

 *   [ Alex Hedström ](https://profiles.wordpress.org/alexhedstrom/)

[Перекладіть “EssentialHeaders” на вашу мову.](https://translate.wordpress.org/projects/wp-plugins/essentialheaders)

### Цікавитесь розробкою?

[Перегляньте код](https://plugins.trac.wordpress.org/browser/essentialheaders/),
перегляньте [сховище SVN](https://plugins.svn.wordpress.org/essentialheaders/) або
підпишіться на [журнал розробки](https://plugins.trac.wordpress.org/log/essentialheaders/)
за допомогою [RSS](https://plugins.trac.wordpress.org/log/essentialheaders/?limit=100&mode=stop_on_copy&format=rss).

## Журнал змін

#### 1.0.2

 * Add: manage X-Powered-By by removing it when its value is blank or replacing 
   it with a custom value.
 * Improve: enforce managed header replacement at the latest applicable WordPress
   header hooks.

#### 1.0.1

 * Fix: always send security headers on front-end HTML even when the request Accept
   header prefers JSON. Skipping those requests let page caches store header-less
   responses and broke scanner results after cache warm-up.

#### 1.0.0

 * Initial release.

## Мета

 *  Версія **1.0.2**
 *  Останнє оновлення **2 тижні тому**
 *  Активних встановлень **10+**
 *  Версія WordPress ** 6.3 або вище **
 *  Tested up to **7.1**
 *  Версія PHP ** 7.4 або вище **
 *  Мова
 * [English (US)](https://wordpress.org/plugins/essentialheaders/)
 * Позначки
 * [csp](https://uk.wordpress.org/plugins/tags/csp/)[headers](https://uk.wordpress.org/plugins/tags/headers/)
   [hsts](https://uk.wordpress.org/plugins/tags/hsts/)[http](https://uk.wordpress.org/plugins/tags/http/)
   [security](https://uk.wordpress.org/plugins/tags/security/)
 *  [Розширений перегляд](https://uk.wordpress.org/plugins/essentialheaders/advanced/)

## Оцінки

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/essentialheaders/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/essentialheaders/reviews/)

## Учасники

 *   [ Alex Hedström ](https://profiles.wordpress.org/alexhedstrom/)

## Підтримка

Є що сказати? Потрібна допомога?

 [Перейти в форум підтримки](https://wordpress.org/support/plugin/essentialheaders/)