PageForge 1.3: check every run before it writes, update generated pages, spintax and resumable batches. See what changed
Account Get it free
Hiperlink Security icon
Actively maintained Tested with WP 7.1 #40 in 2FA

Hiperlink Security

Lightweight WordPress security plugin: two-factor login (2FA), hardening, security headers with CSP, activity log and site check. No upsell.

Active installs30+10+ tier
Downloads · 30d396• 0% vs prev. 30d
Rating—0 reviews
Health score67/100Good
All-time downloads447Since Nov 2026
Support resolved—No recent threads
RequiresWP 6.0PHP 7.4+
Downloads · 7d396• 0% week over week
Our verdict

Solid choice

Hiperlink Security is a solid plugin choice in 2026, with a few things worth checking first. It runs on 30+ sites and was last updated 2 hours ago, and scores 67/100 on our health check.

  • Actively developed — last update 2 hours ago
  • Tested with the latest WordPress (7.1)
  • Small user base (30+ active installs)
  • Very few reviews so far

How does it stack up?

Side-by-side on installs, updates, ratings & support

Daily downloads

244973Nov 15Nov 17Nov 19
Yesterday98
Daily average (1y)79
Peak day98Nov 19, 2026
Last 12 months396

Download spikes usually follow a new release — each site that auto-updates counts as a download.

Rankings

Where Hiperlink Security stands today

WordPress.org search rankings

Live position in the plugin search, top 100
KeywordPositionCompeting pluginsCategory
2FA >100 483 Best 2FA plugins →
content security policy >100 6,520 Best content security policy plugins →
hardening >100 2,690 Best hardening plugins →
security >100 10,000 Best security plugins →
Security Headers >100 7,137 Best Security Headers plugins →

Version adoption

Share of active sites per release.

  • 1.1100.0%

About Hiperlink Security

From the official readme · v1.1.22

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.
  • Security alerts (off until you turn it on): emails you about new administrators, installed plugins, changed security settings and logins from new networks.
  • 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, a tab per module 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-By header 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 cannot be used to guess passwords (many at a time through system.multicall), and only administrators keep application passwords for the REST API. 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.
  • Turn off the theme and plugin file editor, as DISALLOW_FILE_EDIT does.
  • 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_language cookie, 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 your site’s missing page.

  • 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, WooCommerce My account, password-protected posts, the REST API and XML-RPC keep working.
  • Forgot it? define( 'HIPERLINK_SECURITY_LOGIN_URL_OFF', true ); in wp-config.php or wp hiperlink-security login-url off switches 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.
  • 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-ancestors follows it.
  • Referrer-Policy: strict-origin-when-cross-origin, a stricter value, or off.
  • Permissions-Policy: camera, microphone, geolocation, USB and ad topics off.
  • Strict-Transport-Security (HSTS), off by default: 5 minutes to 2 years, with clear warnings. includeSubDomains and preload are 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 what a CDN, cache or plugin changed.

Content Security Policy in four steps:

  1. 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).
  2. Report-Only: browsers report what the policy would block, without blocking anything.
  3. 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.
  4. Enforce: one click and a confirmation send the real Content-Security-Policy header. You can go back at any time.

Site check module

A WordPress security checklist with a score out of 100: 29 checks run from inside your site, and each item that needs work gets one plain sentence on fixing it. 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.

Leftovers of a break-in

  • Administrator roles, sessions and application passwords of users that do not exist.
  • Keys of removed remote management plugins, file manager backups, find-and-replace rule tables.
  • Spam categories and tags, spam pages and other non-media files in uploads, hidden marker files.
  • Tables of removed plugins and inactive themes.

A check that cannot run shows Not checked and does not count. The score averages Security, Hardening and Email, plus Leftovers when something is found; 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 and reads your domain’s DNS records.

Activity log module

A WordPress activity log (audit log) that stays small:

  • What it records: logins and failed logins, password, email, two-factor and application password changes, users and roles, plugin, theme and WordPress changes, published and deleted content, saved settings, and registration, site address and admin email changes from any source. Each entry has the time, the user, the action and its object.
  • 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.

Security alerts module

Emails about what an attacker does after getting in:

  • A new administrator, or a user given the administrator role.
  • A plugin or theme installed, a plugin switched on, the theme switched.
  • Registration opened, the default role or the site address changed.
  • Two-factor login turned off for an administrator, or a new application password.
  • An administrator logging in from a network their account has not used before: that email goes to them.

One email per page load, at most 20 an hour, sent through WordPress.

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 comment menus, settings, editor boxes, column, widgets and admin bar item are removed.
  • Comment endpoints close: wp-comments-post.php, the REST API routes, XML-RPC methods and comment feeds.
  • 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. 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. 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.

Hide footprints module

Scanners such as WPScan find plugins by their readme files, folders and versions, then try known holes. This makes that harder; keep updating.

  • 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.
  • 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.

Installation

  1. Install the plugin from Plugins > Add New, or upload the hiperlink-security folder to /wp-content/plugins/.
  2. Activate it. Hardening and Site check work straight away with safe defaults.
  3. Review the modules under Settings > Security, and turn on Security headers when you are ready to test the headers and the Content Security Policy.

Changelog

1.1.22

  • Site check, Leftovers: files that plugins keep in uploads on purpose (WP All Import’s custom functions, WPML’s template cache and changelog, Really Simple SSL’s test file, SeedProd’s help) no longer count as files that do not belong there. Before, WP All Import’s functions.php made a shop fail the check as spam. More can be added with the hiperlink_security_site_check_known_uploads filter.

1.1.21

  • Site check: seven new checks for leftovers of a break-in, made from a real cleanup. They find administrator roles, login sessions and application passwords kept for users that no longer exist; keys and tools that removed plugins left behind (ManageWP Worker keys and its scheduled task, WP File Manager backups, Real-Time Find and Replace rules); empty spam categories and tags; spam pages, logs and other files in uploads that are not media, and folders there named like a domain; hidden or empty marker files in wp-content; tables of removed plugins; and inactive themes. They read only your database and files. Leftovers count in the score only when something is found, so a clean site keeps its score.

1.1.20

  • New Security alerts module (off until you turn it on): an email when an administrator is added, a plugin or theme is installed, a plugin is switched on, the theme is switched, registration is opened, the default role or the site address changes, or an administrator’s two-factor login is turned off or gets a new application password. Administrators get their own email when they log in from a network their account has not used before. One email per page load, at most 20 an hour, sent through WordPress.
  • Hardening: a new option turns off the theme and plugin file editor, as DISALLOW_FILE_EDIT in wp-config.php does. Site check links to it.
  • Two-factor login on multisite: the code is asked on every site of the network, also on sites where the module is off, because the login cookie works on all of them. Before, a site with the module off let those users in with the password alone.
  • Limit failed logins behind a trusted proxy: choose the header the proxy sets (X-Forwarded-For or X-Real-IP). Only that header is read, so a visitor cannot pick an address by sending the other one.
  • Trusted proxies saved in IPv6 form (::ffff:10.0.0.1 or ::ffff:10.0.0.0/104), as the Hardening tab showed the address on some dual-stack servers, are recognised again; before, every visitor counted as the proxy and the login limit could lock everyone out together.
  • Form antispam: saving its settings clears Hiperlink Cache, so cached pages get the protection fields of a form you just switched on.
  • Custom login address: a new address is kept only when it shows the login form; another page answering there (a theme’s catch-all, a cached copy) brings the old address back, so you are not locked out after logging out.
  • Custom login address: links to wp-login.php in WordPress emails go to the login address, also when a visitor’s request or WP-Cron sends them, for example the set-password link after registering on the site. The recovery mode link stays on wp-login.php.
  • Site check: a Content-Security-Policy counts as passed only when it limits scripts (script-src or default-src, without *), and frame-ancestors * no longer passes. The login limit and two-factor results say what the check found, not what is certain. From WP-CLI right after an update the last known Updates result stays instead of “Not checked”. No doubled full stop after dates.
  • Hide footprints: old-style inline scripts and styles wrapped in an HTML comment are no longer removed with “Remove generator tags and comments”. Browser files such as license.js or readme-banner.png are no longer hidden. The check allows for missing pages that change a little on every request (random posts, a nonce), so it no longer reports those plugins as visible.
  • Two-factor login: the secret behind the app codes is stored encrypted, with a key made from the site’s salts. Secrets saved by earlier versions are encrypted the first time they are used. If you change the salts in wp-config.php, each user sets two-factor login up again (backup codes keep working until then).

1.1.19

  • Settings: the Settings > Security page shows the Hiperlink logo next to its title and a link to the plugin’s maker. This is in the dashboard only; nothing changes on the site visitors see.
  • Activity log: entries older than “Keep entries for” are removed with the next logged event and never shown or exported, also on quiet sites. Before, they were removed only every 100th event.
  • Activity log: a failed login with a real user name shows that name in the User column, and the User filter finds it.
  • Site Check: when the site cannot load its own home page, the other requests are no longer made one after another, so the check finishes in seconds instead of running past the server’s time limit.
  • Site Check: readme.html and license.txt count as open only when the answer is the file itself, so a coming-soon page or a site that answers every address no longer reads as an open readme. When a firewall or password protection answers the home page with an error, the other “closed” results are not counted as passed.
  • Site Check: “Login names” looks only at the body classes of the author archive, so a comment by that user on another page no longer warns. A user called admin who cannot write or change anything (a subscriber, a shop customer) no longer warns. An old wp-content/debug.log left from earlier debugging now warns.
  • Site Check: reports built by WP-Cron (for example Hiperlink Connect’s) include the score.
  • Security headers: WordPress’s /embed/ pages can be shown in frames on other sites again. A keyword typed without quotes (self, none) is saved as the keyword, not as a host name. Turning Basic protection back on keeps an advanced choice sent in the same form. HSTS can be taken back with max-age 0.
  • Login limit and Activity log: an IPv4 address that a dual-stack server reports as ::ffff:… is read as plain IPv4, so Cloudflare’s edge is recognised there too.
  • Hiperlink Cache: saving the module choice, Security headers, Hardening or Hide footprints clears its saved pages, so visitors get the new headers at once.
  • Two-factor login: on a network in folders, opening the login page while logged in no longer counts as a failed login.
  • Custom login address: only the letters a to z, numbers, hyphens and underscores are accepted. Other letters were saved in a form that never matched, which could lock you out.

1.1.18

  • Custom login address (security fix): some variations of the wp-login.php address could still show the login form to visitors. wp-login.php now decides as WordPress does, so they get the missing page.
  • Custom login address: the link in WordPress’s recovery mode email works again. It stays on wp-login.php, where WordPress checks it, and after it wp-login.php sends you on to the login address.
  • Hide footprints: turning it off and another module on in the same save no longer leaves quiet mode on for the other Hiperlink plugins.
  • Site Check: an HSTS max-age of 180 days, the Headers module’s “6 months”, now passes. A server that drops xmlrpc.php or http:// without an answer no longer hides the whole score. HTTPS is read from the saved Site Address, not from the scheme of the dashboard you opened. On a network, SPF and DMARC are read for the domain WordPress sends mail from.
  • Hardening: with “Hide user names”, an unknown name on the lost password form gets exactly the redirect a real account gets.
  • Comments off: WooCommerce review moderation (Approve, Trash and Spam in the email, Edit under Products > Reviews) works again.
  • Two-factor login: its user meta is protected, so REST APIs that list user meta, such as WooCommerce’s customers endpoint, leave the secret out.
  • Readme: on a network, two-factor login asks for the code only on sites where the module is on.

1.1.17

  • Site Check: the “Login names” check no longer warns when ?author= redirects to the home page of a domain whose name equals the author slug (for example the user “example” on example.com). Only a redirect whose path contains the slug, such as /author/example/, counts as showing the login name.

Full changelog on WordPress.org →

Screenshots

Site check gives a security score and a plain fix for each item.
Site check gives a security score and a plain fix for each item.
Each module can be switched on or off on its own.
Each module can be switched on or off on its own.
Hardening hides login names and software versions and turns off pingbacks.
Hardening hides login names and software versions and turns off pingbacks.
Security headers shows what your home page sends and which headers to add.
Security headers shows what your home page sends and which headers to add.

For developers

Is this your plugin? Show off the numbers.

Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.

Active installs badge Rating badge Health score badge

Best Hiperlink Security alternatives

All 2FA plugins →
Alternatives
Rank Plugin Active installs Rating Updated Health
1 Wordfence Security – Firewall, Malware Scan, and Login Security Wordfence Security Firewall, Malware Scanner, Two Factor Auth, and Comprehensive Security Features, powered by… by Mark Maunder 5M+ ★★★★★★★★★★ 4.7 (5.1K) 1 week ago 96
2 Really Simple Security – Simple and Performant Security (formerly Really Simple SSL) Really Simple Security Easily improve site security with WordPress Hardening, Two-Factor Authentication (2FA)… by Really Simple Plugins 3M+ ★★★★★★★★★★ 4.9 (8.9K) 4 weeks ago 97
3 Limit Login Attempts Security – Login Security, 2FA, Firewall, Brute Force Prevention Limit Login Attempts Security WordPress login security with brute force protection, Two-factor authentication (2FA/MFA)… by WPChef 1M+ ★★★★★★★★★★ 4.8 (1.5K) 24 hours ago 87
4 Two Factor Two Factor Enable Two-Factor Authentication (2FA) using time-based one-time passwords (TOTP), email… by WordPress.org 100K+ ★★★★★★★★★★ 4.8 (209) 2 months ago 87
5 WP 2FA – Two-factor authentication for WordPress WP 2FA – Two-factor authentication for WordPress Get better WordPress login security; add two-factor authentication (2FA) for all your users… by Melapress 100K+ ★★★★★★★★★★ 4.7 (184) 1 week ago 88
6 All In One Login All In One Login Secure and customize your WordPress login page with a custom login URL, 2FA, CAPTCHA, and… by Saad Iqbal 60K+ ★★★★★★★★★★ 3.6 (35) 1 week ago 88
7 WP Hide & Security Enhancer WP Hide & Security Enhancer Protect your website by concealing vulnerable WordPress traces, plugins, themes… by nsp-code 50K+ ★★★★★★★★★★ 4.3 (275) 1 week ago 92
8 Security Plugin, Firewall & Malware Scanner with Auto Removal Security Plugin, Firewall & Malware Scanner with Auto Remov… Protect WordPress from malware, hackers, brute-force attacks & suspicious traffic. Includes… by CleanTalk Inc 40K+ ★★★★★★★★★★ 4.8 (398) 2 weeks ago 94
9 Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning Shield Security Smart WordPress security that blocks bots automatically, guides you to what matters, and… by Paul 30K+ ★★★★★★★★★★ 4.8 (1K) 3 weeks ago 94
10 Two Factor Authentication Two Factor Authentication Secure WordPress login with Two Factor Authentication - supports WP, Woo + other login… by David Anderson / Team Updraft 20K+ ★★★★★★★★★★ 4.4 (77) 2 days ago 87

FAQ

Hiperlink Security: quick answers

Straight answers, pulled from live WordPress.org data.

Source: WordPress.org

Is Hiperlink Security free?

Yes. Hiperlink Security is free to download and use from the official WordPress.org plugin directory.

Is Hiperlink Security safe to use in 2026?

Hiperlink Security is a solid plugin choice in 2026, with a few things worth checking first. It runs on 30+ sites and was last updated 2 hours ago, and scores 67/100 on our health check.

How many websites use Hiperlink Security?

Hiperlink Security is active on 30+ WordPress websites and has been downloaded 447 times since it launched in November 2026. It was downloaded 396 times in the last 30 days.

Does Hiperlink Security work with WordPress 7.1?

Yes. The developer has tested Hiperlink Security up to WordPress 7.1.5, the latest release. It requires WordPress 6.0 or newer.

What PHP version does Hiperlink Security need?

Hiperlink Security requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.

When was Hiperlink Security last updated?

The latest version, 1.1.22, was released on November 20, 2026 (2 hours ago).

Who makes Hiperlink Security?

Hiperlink Security is developed and maintained by Hiperlink Digital.

What are the best alternatives to Hiperlink Security?

The most popular alternatives to Hiperlink Security are Wordfence Security (5M+ installs), Really Simple Security (3M+ installs) and Limit Login Attempts Securi… (1M+ installs).

Powered by PageForge

One template and a spreadsheet. A real page for every search.

PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.

  • CSV and XLSX, plus Google Sheets on Professional and Enterprise
  • Its own title, URL, SEO fields and schema for every page
  • Works with the block editor, Elementor, Divi and Avada
  • Free on WordPress.org, no credit card

↑↓ to move↵ to open