Hiperlink Security Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Hiperlink Security is a lightweight WordPress security plugin with two-factor authentication (2FA), hardening, security headers and a security checklist, made of modules you can switch on and off under Settings > Security. It does not call any outside service, does not load anything from other sites and sets no cookies.
- Hardening (on by default): stops user enumeration, turns off pingbacks and hides software versions. Optional: a failed login limit and password logins only on the login page.
- Custom login address (off until you turn it on): moves the login page to an address you choose, so bots find no login form at wp-login.php.
- Two-factor login (off until you turn it on): a code from an authenticator app after the password, with backup codes; can be required for administrators.
- Security headers (off until you turn it on): the HTTP security headers scanners look for, and a Content Security Policy rolled out safely through Report-Only mode with CSP reports collected on your own site.
- Site check (on by default): a WordPress security checklist with a score out of 100, on the dashboard and in its own tab.
- Activity log (off until you turn it on): who logged in, failed logins, account security, user, plugin, theme and core changes, published and deleted content and saved settings.
- Comments off (off until you turn it on): closes and hides comments everywhere, for sites that do not use them.
- Form antispam (off until you turn it on): stops spam bots in the comment form, Contact Form 7, WPForms, Elementor Pro and Fluent Forms without a CAPTCHA.
- Hide footprints (off until you turn it on): hides which plugins your site uses from visitors and scanners. It makes automated targeting harder; it does not replace updates.
Why Hiperlink Security
- No weight for visitors: with the default modules, +0 database queries on an uncached page (about +130 KB of memory in our measurements) and no script, stylesheet or inline JavaScript. With every module on, still +0 queries.
- Nothing leaves your site: no account or API key; 2FA QR codes are made on your server and CSP reports go to your own site.
- Simple: one settings page with a tab for each module that has settings, and safe defaults; a module that is off is not loaded.
- No ads, upsell notices or tracking. Deleting the plugin removes everything it stored.
Works with: WooCommerce (two-factor login and the login limit on My account and checkout), Contact Form 7, WPForms, Elementor Pro and Fluent Forms, Polylang, page caches such as Hiperlink Cache, multisite, and next to Wordfence or Solid Security (tested with all modules on).
Hardening module
Stop user enumeration
- Author archives (
/?author=1,/author/name/) return 404 for visitors who are not logged in. - The REST API users routes (
/wp-json/wp/v2/users) are removed for visitors who are not logged in. The block editor keeps working. - The users sitemap and the author name in oEmbed data are removed.
- A failed login and the lost password form give the same answer, so they no longer say whether a user name exists.
- The tab warns about users who publish under their login name, which feeds show.
Turn off pingbacks and trackbacks
- Publishing does not make your server connect to linked sites or ping services, so its address stays private.
- Incoming pingbacks over XML-RPC and trackbacks are closed, and the X-Pingback header is removed.
Hide software versions
- Removes the
X-Powered-Byheader with the PHP version, the WordPress generator tag and the WordPress version in?ver=of scripts, styles and script modules (a hash that still changes with each update).
Optional
- Password logins only on the login page: xmlrpc.php refuses every login with a user name and password, so it can no longer be used to guess passwords, many at a time through
system.multicall, and only administrators keep application passwords for the REST API (other users’ existing ones stop working). Off by default, because the WordPress mobile app, desktop blog editors and some Jetpack features log in through XML-RPC. - Limit failed logins: after 5 failed logins from one address, each within 15 minutes of the one before, that address cannot log in for 15 minutes (login form, XML-RPC, application passwords). Addresses are kept only as a keyed hash. Behind Cloudflare visitors’ addresses are read correctly; behind another proxy once you list it as trusted.
- Remove readme.html and license.txt from the site root now and after every core update, because readme.html shows the WordPress version.
- Polylang: no
pll_languagecookie, for sites that always keep the language in the URL.
Custom login address module
Bots try passwords at wp-login.php on every WordPress site. With your own address they find no login form: wp-login.php and wp-admin show visitors who are not logged in your site’s missing page, exactly as for any address that does not exist.
- The address appears only on the login page and for logged-in users, never in pages, redirects or headers for other visitors.
- Two-factor login, password reset and registration emails, the WooCommerce My account login, password-protected posts, the REST API and XML-RPC keep working. Page caches never save the login page.
- Forgot it?
define( 'HIPERLINK_SECURITY_LOGIN_URL_OFF', true );in wp-config.php orwp hiperlink-security login-url offswitches it off.
Two-factor login module
Two-factor authentication (2FA) for WordPress logins with an authenticator app, made entirely on your site: no SMS, no outside service, no account anywhere.
- Authenticator apps: time-based one-time passwords (TOTP, RFC 6238) that work with Google Authenticator, Microsoft Authenticator, Authy and other apps.
- Setup in the profile: each user scans a QR code made on your own server (the secret never goes to a QR service), or types the key, and confirms with a code.
- 10 backup codes: each logs in once without the phone. They are stored hashed and shown only once.
- Require it for administrators, with a grace period of up to 30 days. After it, an administrator without two-factor login sees only their profile until they set it up.
- No way around it: the login cookie is set only after the code. XML-RPC and other logins with the password alone are refused for these users. Application passwords keep working for apps, because only a user who passed two-factor login can create one.
- Works with the login limit: wrong codes count like wrong passwords.
- Lost phone: another administrator resets it in the user’s profile, or the host runs
wp hiperlink-security 2fa reset <user>.
Security headers module
Adds the HTTP security headers that scanners look for, with defaults that do not break WordPress, and rolls out a Content Security Policy the safe way: first in Report-Only mode with CSP reports collected on your own site, then enforced.
- X-Content-Type-Options: nosniff, so an uploaded file cannot run as a script.
- X-Frame-Options: SAMEORIGIN or DENY against clickjacking; with the CSP on,
frame-ancestorsfollows it. - Referrer-Policy: strict-origin-when-cross-origin, a stricter value, or off.
- Permissions-Policy: camera, microphone, geolocation, USB and ad topics off; payment stays allowed for shop wallets.
- Strict-Transport-Security (HSTS), off by default: 5 minutes to 2 years, with clear warnings.
includeSubDomainsandpreloadare never on by default. - Status check: Check now requests your home page as a visitor, also past the page cache, and shows each header received next to the one sent, so you see when a CDN, the server, a cache or another plugin overrides, drops or doubles one.
Content Security Policy in four steps:
- Scan the home page, the newest post and page and the shop page, and build the policy from
'self'plus the outside scripts, styles, fonts, images, frames, media and form targets they load (Google Fonts and Analytics included). - Report-Only: browsers report what the policy would block, without blocking anything.
- Allow: blocked sources are listed by directive with a count, the last time and the page. Allow trusted ones in one click, or ignore them.
- Enforce: one click and a confirmation send the real
Content-Security-Policyheader. You can go back at any time.
Every directive can also be edited by hand; invalid sources are removed, so a typo cannot break the header.
Site check module
A WordPress security checklist with a score out of 100: 22 checks run from inside your site, and each item that needs work gets one plain sentence on fixing it. The results are on the dashboard and under Settings > Security > Site check. When another module can fix an item, the result names the module.
HTTPS and security headers
- The site address uses HTTPS, and http:// redirects to https://.
- Security headers on the home page: Strict-Transport-Security (HSTS), X-Frame-Options or frame-ancestors, Content-Security-Policy (including report-only mode), X-Content-Type-Options and Referrer-Policy.
WordPress hardening audit
- Pending WordPress, plugin and theme updates, read from WordPress’s own update data.
- PHP version: whether it still gets security fixes, and for how long.
- User enumeration through the REST API users route and
?author=1. - XML-RPC that accepts logins or pingbacks, and no limit on failed logins.
- readme.html and license.txt that anyone can open.
- Downloadable backups: wp-config.php copies, .env, .git, database dumps, archives and a listed uploads folder.
- PHP and WordPress versions in the X-Powered-By header or the generator tag.
- Errors shown on pages (WP_DEBUG_DISPLAY, display_errors) and a debug log inside the web root.
- The plugin and theme code editor in the dashboard (DISALLOW_FILE_EDIT).
- A user named “admin”, and open registration with a powerful default role.
- Administrators without two-factor login.
Email security: SPF and DMARC
- The SPF record of your domain and how it ends (-all, ~all, ?all or +all), following redirect=.
- The DMARC policy (none, quarantine or reject), also on the parent domain for subdomains.
A check that cannot run, for example when the host blocks the site’s requests to itself, shows Not checked and does not count. The score averages three areas, Security, Hardening and Email; problems attackers use more often count more.
The check runs only when you press “Check now”. It asks your own site for a few pages as a visitor and reads your domain’s DNS records; nothing is sent anywhere else.
Activity log module
A WordPress activity log (audit log) that stays small:
- What it records: logins, logouts and failed logins, password resets, password, email, two-factor and application password changes, user and role changes, plugin, theme and WordPress installs, updates and removals, published, trashed and deleted content, saved settings pages, and registration, site address and admin email changes from any source. Each entry has the time, the user, the action and what it was done to.
- What it does not record: passwords, content, or IP addresses unless you choose to store them. A failed login with a user name that does not exist is logged without the typed name.
- Stays small: failed logins are counted per user name and hour, so an attack adds a few rows, not thousands. Old entries go after 30 to 365 days (90 by default), and the log keeps about the newest 10,000.
- List and export: filter by action, user and period, and download the result as a CSV file that is safe to open in a spreadsheet.
Comments off module
For sites that do not use comments. It replaces a separate “disable comments” plugin:
- Comments, pingbacks and trackbacks are closed on every post, page and custom post type, and existing comments are no longer shown, also in block themes.
- The Comments menu, Discussion settings, editor boxes, comment column, Recent Comments widget, dashboard widget comments and admin bar item are removed.
wp-comments-post.phpanswers 403, the REST API comments routes and the XML-RPC comment and pingback methods are removed, comment feeds answer 404 and the X-Pingback header is gone.- Nothing is deleted: switch the module off and the comments are back.
Form antispam module
Stops spam bots without a CAPTCHA, a cookie or an outside service, and without slowing visitors down: nothing runs in the browser.
- Honeypot: a text field that people never see. Bots fill in every field, so a submission with something in it is refused.
- Minimum fill time: the form carries the time it was made, signed with your site’s secret keys, so it cannot be forged or moved to another form. Bots send a form the moment they load it; anything faster than 3 seconds (or 2, 5 or 10) is refused, as are submissions without the signed time.
- Comment form, Contact Form 7, WPForms, Elementor Pro and Fluent Forms out of the box (not Fluent Forms conversational forms). Logged-in users are not checked in the comment form, and other forms can use two filters (see the FAQ).
- Only a count is kept: the number of blocked submissions per day for 30 days, never their content or IP addresses. Each form shows the refusal in its own way; the comment form asks to wait and send again.
Hide footprints module
Scanners such as WPScan find plugins by their readme files, folders and version numbers, then try their known holes. This makes that harder; keep updating, because a vulnerable plugin stays vulnerable.
- Plugin files: readme, changelog, translation and build files and plugin folders answer like files that do not exist. The rules go at the top of
.htaccess(Apache, LiteSpeed); for nginx the tab shows them. A check tests the result. - Versions: other plugins’ scripts and styles get a version that cannot be matched to a release.
- Quiet mode: Hiperlink plugins use your site’s own names in pages, cookies and addresses (also with
HIPERLINK_QUIETin wp-config.php). - Optional: removes other plugins’ generator tags and comments.
Nothing is hidden from administrators; turning it off undoes everything.
The plugin is made by Hiperlink Digital, a web agency from Croatia that builds, maintains and protects websites. We run the same code on our own site.
External services
Hiperlink Security uses no outside service: it sends nothing about your site, users or visitors anywhere and loads nothing from other sites.
- Hosts in the Content Security Policy (Security headers module, off by default). When your pages already load Google Analytics, Google Tag Manager or Google Fonts, the suggested policy also allows the hosts these tools use (
*.googletagmanager.com,*.google-analytics.com,*.analytics.google.com,fonts.gstatic.com). The plugin only writes these names into the header your site sends and never requests them. Whether browsers contact Google depends only on the tags or fonts you added yourself: Google terms, privacy policy. - Your own site and domain. Some checks open your own pages as a visitor, and Site check reads your domain’s SPF and DMARC records.
- A link. The Site check tab links to a free outside check on hiperlink.digital; nothing is sent unless you open it.
Screenshots
Site check gives a security score and a plain fix for each item.
Each module can be switched on or off on its own.
Hardening hides login names and software versions and turns off pingbacks.
Security headers shows what your home page sends and which headers to add.

