Site settings

Security settings

Kufi → Settings protects your site from common automated attacks out of the box. Here's what each option does and when to change it.

Go to Kufi → Settings → Security. The defaults are safe for most sites. Every option also has a short explanation on the screen.

Hide WordPress fingerprints

Removes the tags that tell bots which WordPress version you run (generator tags, version strings), plus emoji and embed scripts most sites don't need. Leave on.

Send security headers

Tells browsers not to let other sites show your pages in a frame, not to guess file types, and to always use HTTPS once visited (HSTS, only on HTTPS sites). Leave on.

Turn off XML-RPC

XML-RPC is an old remote-publishing interface that bots use to guess passwords. Leave on, unless something you use needs it, such as the old WordPress mobile app or Jetpack.

Block username discovery

Stops bots from finding login names through author pages, the public user list in the REST API, the user sitemap and embed previews. Leave on, unless your blog shows author archive pages.

Kufi also gives the same answer for a wrong username and a wrong password on the login screen ("Those details didn't work. Try again."), so the login page doesn't confirm which usernames exist.

Require login for the REST API

Off by default. Turning it on hides site data from the public WordPress API. WooCommerce's Store API stays open, so the cart and checkout keep working. Some plugins, apps and headless setups need the public API, so test your site after turning it on.

Content Security Policy

Choice What it does
Enforce (recommended) Browsers only run scripts that your site added itself. Injected scripts are blocked for visitors.
Report only Nothing is blocked; the browser lists what would be blocked in its console. Use it to test a new plugin.
Off No policy.

The policy applies to visitors who aren't logged in. Cart, checkout and account pages get a relaxed policy, because payment providers load scripts from their own servers.

If a plugin or embed stops working for visitors, see Something is blocked by the Content Security Policy.

Form submissions

How many messages one visitor can send through Kufi contact forms in 10 minutes. 5 to start. It stops spam floods; real visitors rarely send more than one.

Serve theme assets from /assets/

Hides /wp-content/themes/ from your page source. Off by default, and it needs a server rule first, otherwise styles and scripts stop loading. On Apache or LiteSpeed hosting, add this to the .htaccess file in your site folder, above the WordPress rules:

RewriteRule ^assets/builder/(.*)$ /wp-content/themes/kufi/builder/assets/$1 [L]
RewriteRule ^assets/(.*)$ /wp-content/themes/kufi/assets/$1 [L]

Then turn the setting on and check a page while logged out. If the page looks unstyled, turn the setting off again and check the rule.

Allow comments on blog posts

Off closes comments on every post. Pages never take comments either way.

Always on

  • File editing in WordPress (Appearance → Theme File Editor) is turned off, so a stolen admin login can't change your code from the dashboard.
  • Layouts are stored as data, never as HTML or code, and checked on every save.
  • Video and map embeds only load from YouTube, Vimeo, Google Maps and OpenStreetMap.
  • Use strong, unique passwords and two-factor login for administrators (with a security plugin).
  • Keep WordPress, Kufi and every plugin up to date.
  • Turn on daily backups at your host.

More in Site settings

Still need help?

Tell us what you are trying to do and what you see. We read every message.