How is my WordPress site protected?

HTTPS everywhere, no code editing from WP Admin, XML-RPC blocked, limits on wrong passwords and signed one-click sign-in links: what Phluit sets up for every site.

Updated November 19, 2026 · 2 min read · Managed WordPress: WordPress management

Every Phluit Managed WordPress site gets the same protections, set up for you. You can see them for each site under Advanced → Security in My Sites.

What's switched on for every site

  • HTTPS certificate. Free, issued and renewed automatically for every address of the site. See Free SSL certificates.
  • Force HTTPS. Every http:// request is redirected to https://, on all addresses. This is always on.
  • File editor in WP Admin: off. Editing plugin and theme code from WP Admin is turned off, so a stolen password can't be used to inject code.
  • XML-RPC: blocked. It's an old way for apps to talk to WordPress and is mostly used for password-guessing attacks.
  • One-click sign-in: protected. The WP Admin links in the portal are signed, can be used only once and expire after a minute.
  • Limits on wrong passwords. After 10 failed sign-in attempts from the same address within 15 minutes, WordPress answers "Too many failed sign-in attempts. Please wait 15 minutes and try again."
  • A private database. The database and its password are managed for you and never leave the server; your site reaches it on a private network.
  • Tested WordPress versions. WordPress itself is updated from the portal, with a backup first. See Automatic updates and updating WordPress.

What you can do yourself

  • Keep plugins and themes up to date, or switch on automatic updates. See Managing plugins from My Sites.
  • Remove plugins and themes you don't use. Unused code can still have security holes.
  • Give people the lowest role they need and remove accounts that aren't used any more. See Managing WordPress users from the panel.
  • Use strong, unique passwords for every WordPress user, and two-factor sign-in for your Phluit portal account.
  • Keep PHP current. Old PHP versions no longer get security fixes. See Changing your PHP version.

If you think your site was hacked

Restore a backup from before the problem started (Restoring a backup (and undoing a restore)), change the passwords of every WordPress user, and open a support ticket. Hacked site repair is part of Phluit Care Pro: the team removes the malware, cleans up the database and hardens the site.

Good to know

  • A plugin that needs the file editor or XML-RPC (for example, an old mobile app) won't work with them. If you really need XML-RPC, contact support.
Was this article helpful?

Still need help?

Our team answers every request, usually within a few hours.

Contact Support

We use cookies to enhance your experience, provide live chat support, and analyze site traffic. By clicking "Accept", you consent to our use of cookies.

Cookie Policy
Accept