WebHD

SSL & Security Hardening

Sends visitors to the secure address, adds HSTS and the other security headers you choose, finds and fixes insecure (http) addresses in your content, checks which headers the site really sends, and keeps a plain checklist of what is in place and what is not.

Version 1.1.2Updated November 19, 2026Security, Backup & Admin

Get in line

Not open yet No card

Description

Sends visitors to the secure address, adds HSTS and the other security headers you choose, finds and fixes insecure (http) addresses in your content, checks which headers the site really sends, and keeps a plain checklist of what is in place and what is not.

What it does

  • Send visitors to the https address (public pages, with a guard against redirect loops)
  • HSTS in steps from five minutes to one year, on https only, with subdomains and preload each behind a warning and a confirmation tick
  • Permissions-Policy: a ready-made rule denying camera, microphone, location, payment, USB and motion sensors, or your own checked rule
  • Cross-Origin-Opener-Policy choice
  • X-Frame-Options choice for old browsers, alongside Core's own framing rule
  • Stricter Referrer-Policy, sent as a header; a page's own rule still wins
  • Option to send the same headers on the admin
  • Mixed-content scan of published content, by host
  • Mixed-content fix: change one host to https across content, after you confirm it works
  • Ask browsers to load everything over https (upgrade-insecure-requests)
  • Security checklist that reads real state: the address in use, the sign-in cookie, the headers the front page really sends
  • Scheduled re-check with a dashboard notice when something got worse
  • One-click SSL activation (issuing a certificate): certificates belong to whoever hosts the site; on Cloudflare they are automatic Not built yet.
  • Changing or loosening Core's own headers (the content security policy and its framing rule, nosniff): Core keeps these Not built yet.
  • Cross-Origin-Resource-Policy: it can stop pictures and files being used by a CDN or another site of yours, so it is left out Not built yet.
  • Submitting the domain to browsers' preload lists: the header can carry the word, the submission at hstspreload.org is yours Not built yet.
  • Redirecting the admin and the API to https: both are outside a module's reach (HSTS does cover them) Not built yet.
  • Testing that an https address answers before rewriting to it: the owner confirms each host instead Not built yet.
  • Vulnerability notices: they list WordPress plugins with known holes; there is no such list for this platform yet Not built yet.
  • .htaccess rules: there is no web-server rule file here Not built yet.

Stands in for

Really Simple Security.

These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.

What comes across

What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.

From Really Simple Security
Comes across: Whether visitors are sent to https, whether mixed content is fixed, a referrer rule when it is one of the stricter choices offered here, HSTS (switched on for one week, whatever the old length), the cross-origin opener policy, X-Frame-Options, and the permissions policy as the ready-made rule.
Does not: HSTS subdomains and preload (each needs your own switch and tick), the old per-feature permissions list, the WordPress hardening switches, the vulnerability scanner, login protection and two-step sign-in. Each is named in the import report with its reason.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
From Headers Security Advanced & HSTS WP
Comes across: HSTS (switched on for one week to start, never at the old length), your own Permissions-Policy rule or the ready-made one, and the X-Frame-Options choice.
Does not: HSTS subdomains and preload (your own switch and tick here), the hand-written Content-Security-Policy (Core writes the site's own), X-Frame-Options ALLOW-FROM, and headers Core already sends.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.

No importer yet for: WP Encryption.

Using a plugin that is not named here? It is built for your site On The Fly. How that works

Changelog

  1. 1.1.2 November 19, 2026

    Security Hardening 1.1.2: Really Simple Security settings from a site that never switched SSL on are read too, and each hardening switch is named.

  2. 1.1.1 November 18, 2026

    SSL & Security Hardening 1.1.1: on a site that sits in a folder of its host (Core's base setting), the links in its emails and on its screens now carry the folder. The header check reads the site's own home page, not the host's.

  3. 1.1.0 November 17, 2026

    SSL & Security Hardening 1.1.0: an importer for Headers Security Advanced & HSTS WP. HSTS comes over switched on for one week (subdomains and preload stay your own choice), with your own Permissions-Policy rule and the X-Frame-Options choice; its hand-written Content-Security-Policy is reported, because Core writes the site's own.

  4. 1.0.0 November 17, 2026

    SSL & Security Hardening: a safe redirect to https, HSTS in steps you can back out of, Permissions-Policy and other security headers, a mixed-content scan with per-host fixes, and a checklist that reads what the site really sends. Imports Really Simple Security settings.

Get SSL & Security Hardening when WebHD opens

Hold a place for your site.

One form on the home page: your WordPress address, then your email.

Get in line

No card Takes a minute No fake scan