Ironhelm Suite

Security that starts before WordPress does.

A firewall in front of WordPress, login protection, two-step login and passkeys, hardening, nightly file checks and vulnerability alerts with automatic security fixes. Clear words when something happens, and one-click recovery when you lock yourself out.

A firewall that runs first

Where the server allows it, the firewall runs before WordPress loads, so attacks are stopped at the cost of a few microseconds. It recognises fake search-engine bots by checking their DNS.

Passwords are not enough

Two-step login with an app or email code, backup codes, and passkeys (Face ID, Touch ID, Windows Hello, security keys) that cannot be phished.

Know when files change

Every night, WordPress and plugin files are compared with the official copies. Altered core files can be restored in one click; unknown PHP files are flagged.

11 Security features

Each one switches on and off on its own. Details and settings are in the Security guide.

  • FirewallOn after setup

    Stops attacks before they reach WordPress: hacking attempts, attack tools, fake Google bots, and countries or addresses you choose.

  • File integrity and malware checkOn after setup

    Checks WordPress and plugin files against the official copies every night, finds hidden PHP files and known malware, and restores altered core files in one click.

  • Vulnerability checkOn after setup

    Warns when WordPress, a plugin or a theme has a known security hole, was pulled from WordPress.org, or has been abandoned, and installs security fixes automatically.

  • Login protectionOn after setup

    Stop bots from guessing passwords by pausing logins from addresses that keep getting it wrong.

  • Two-factor loginOn after setup

    Ask for a code from a phone app or email after the password, so a stolen password is not enough.

  • PasskeysOn after setup

    Sign in with Face ID, Touch ID, Windows Hello or a security key instead of a password. Phishing-proof, and counts as two-factor login.

  • HardeningOn after setup

    Close the weak spots attackers check first, and hide the clues that tell them which version you run.

  • Security headersOn after setup

    Tell browsers how to protect your visitors: force HTTPS, block clickjacking and limit what pages may load.

  • Spam shieldOn after setup

    Keep bots out of comments, contact forms, sign-ups and logins, with invisible checks first and a CAPTCHA only where you want one.

  • Safe SVG uploadsOptional

    Let chosen roles upload SVG logos and icons, cleaned of anything that could run code.

Security is in every plan.

So is everything else.