Vishwa

vishvega

HeaderShield adds a conservative set of security headers that improve browser protection without breaking most sites. It also provides optional strict cross-origin protections for sites that are ready for them.
Default headers include:
<ul>
<li>X-Frame-Options</li>
<li>X-Content-Type-Options</li>
<li>X-XSS-Protection (legacy)</li>
<li>Referrer-Policy</li>
<li>Permissions-Policy</li>
<li>Content-Security-Policy (upgrade-insecure-requests)</li>
<li>Strict-Transport-Security (HTTPS only)</li>
</ul>
Strict Mode can additionally enable COEP, COOP, and CORP for stronger isolation, but may break third‑party scripts or embeds. Use with care and test on staging first.
<h4>Source code for third-party assets</h4>
The admin UI uses SlimSelect for the multi-select dropdown. Human-readable source is included in the plugin:
<ul>
<li>JavaScript: <code>assets/js/slimselect.js</code> (minified build: <code>assets/js/slimselect.min.js</code>)</li>
<li>CSS: <code>assets/css/slimselect.css</code> (minified build: <code>assets/css/slimselect.min.css</code>)</li>
</ul>
Upstream project: https://github.com/brianvoe/slim-select (MIT). This plugin does not use a custom build process; the included files are from the published release.

HeaderShield

Add safe, modern HTTP security headers with optional strict cross-origin protections and a simple admin UI.

Simon Waters

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:
<ul>
<li>HSTS (Strict-Transport-Security)</li>
<li>HPKP (Public-Key-Pins)</li>
<li>Disabling content sniffing (X-Content-Type-Options)</li>
<li>XSS protection (X-XSS-Protection)</li>
<li>Clickjacking mitigation (X-Frame-Options in main site)</li>
<li>Expect-CT</li>
</ul>
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.

Security Headers

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

HeaderShield vs Security Headers