Skip to content
// hardening

Website security hardening, done by a developer

Website hardening means removing the easy ways in: switching off what your site doesn't need, tightening what it does, and adding the protective settings most sites are missing. Odesstra is run by a web developer, so we make the changes, test that your site still works, and re-check afterwards. Every job is quoted at a fixed price first.
// what we change

What hardening usually includes

  • HTTPS done properly: a permanent redirect from http://, modern TLS only, HSTS, and a CAA record naming your certificate authority.
  • Security headers: Content Security Policy rolled out in report-only mode first, clickjacking protection, nosniff, Referrer-Policy and Permissions-Policy.
  • Less on show: version numbers removed from the Server and X-Powered-By headers and the generator tag. Check yours with the server version checker.
  • Email protection: SPF tidied up and under the lookup limit, DKIM on for every sender, and DMARC stepped up to enforcement safely.
  • WordPress and CMS clean-up: unused plugins, themes and accounts removed, updates applied, file editing in the WordPress admin switched off, and login protection added.
  • Accounts: two-factor authentication on hosting, registrar, email and admin logins, set up with you.
// how it works

How a hardening job runs

  1. 01

    Start from evidence

    We begin with a free passive check or an audit, so the list is based on what your site actually shows.

  2. 02

    Fixed quote

    You get a list of changes, each with a price. Choose all, some or none.

  3. 03

    Change and test

    We make the changes in a sensible order, test your forms, shop and logins after each one, and keep a note of what was changed so it can be reversed.

  4. 04

    Re-check

    We run the check again and send you the before-and-after, so you can see what improved.

// before and after

What a typical change looks like

// hacker view

[headers] HSTS missing · CSP missing · X-Frame-Options missing · Server: Apache/2.4.41 warn

// plain english

Your site is missing three protective settings and tells strangers its server version. All four are configuration changes, usually done in an afternoon with testing.

Hardening improves your grade on outside checks, but the grade isn't the goal. The aim is fewer easy targets and a site that still works exactly as before. If you're curious what the grade measures, read what does my website security grade mean?.

// honest limits

What hardening can't do

Hardening reduces risk; it can't remove it. It won't fix flaws inside custom code, and it can't stop a new vulnerability being published tomorrow in a plugin you rely on. That's what monitoring is for. If your site may already have been broken into, hardening comes after the clean-up, not instead of it. Start with how to tell if your WordPress site has been hacked.

// questions

Common questions

Will hardening break my website?

It shouldn't, because we test after each change and roll out the riskier settings, such as Content Security Policy, in report-only mode first. Everything we change is written down so it can be undone.

Do you work on platforms other than WordPress?

Yes. Most of the work is server, hosting, DNS and header configuration, which applies to any site. CMS-specific clean-up depends on the platform, and we'll say up front if it's not one we know well.

Do I need monitoring as well?

Not to buy hardening. But settings drift and new flaws appear, so a re-check now and then, or ongoing monitoring, keeps the work from going stale.

Can our agency hand hardening work to you?

Yes. Agencies use us for fix work under their own brand. See white-label website security.

Will this make my site secure?

No honest provider can promise that. Hardening removes many common weaknesses and makes your site a less attractive target, and the re-check shows exactly what changed.

Talk to a human