CensusPlugin profiles › WP 2FA

WP 2FA – Two-factor authentication for WordPress

Figures from the Plugin Directory Census · as of 28 Aug 2026

100,000

Active installs, lower bound

Group: 100,000 to 999,999 installs

17

Days since the last release

Group median: 12

4.7

out of 5, from 176 ratings

Group median: 4.7 (10+ ratings)

50.0%

Support threads marked resolved, two months

Group: 68.2%

Full profile on wordpress.orgShow on the mapCompare with your own plugins

What is WP 2FA and who is behind it?

WP 2FA is a WordPress plugin in the “Security” field, made by Melapress. It has been listed in the directory since 20 Mar 2020, so for 6 years. Melapress has 3 plugins with at least 10,000 installs in the census. With 100,000 to 199,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 17 days before the reference date, and it is tested up to WordPress 7.0.

This is how the author describes the plugin on wordpress.org:

“Get better WordPress login security; add two-factor authentication (2FA) for all your users with this easy-to-use plugin.”

Self-description on wordpress.org, retrieved on 10 Sept 2026

When was WP 2FA last released?

The last release of WP 2FA came 17 days before the reference date; the group median is 12 days.

WP 2FA · 17 days today1 month3 months1 year3 years10 years
Each dot is a plugin in the 100,000 to 999,999 installs group, placed horizontally by days since its last release, on a logarithmic scale. The dashed line marks 365 days.

How many installs does WP 2FA have?

WP 2FA had 100,000 to 199,999 active installs on the reference date. Within its group, 219 plugins had a higher band and 179 plugins the same band.

The API reports installs only as a lower bound with one significant figure: 100,000 means at least 100,000 and at most 199,999.

Which WordPress version is WP 2FA tested with?

No directory notice: tested up to WordPress 7.0, while core stood at 7.1 on the reference date. The notice appears once the field falls below 6.9; that applied to 8.0% of the group.

How does WP 2FA compare with its group?

The group holds 399 listed plugins. 57.6% of them had a more recent last release than WP 2FA; 5.3% had no release for more than 365 days.

FigureWP 2FAGroup, 399 plugins
Days since the last release17median 12
Rating4.7 (176)median 4.7 (10+ ratings)
Support threads marked resolved50.0%68.2%
Tested up to7.047.6% on 7.1
Requires PHP7.4most often 7.4 (41.6%)

All values on the reference date

Slugwp-2fa
AuthorMelapress
Active installs100,000 to 199,999
Last release17 days before the reference date
Tested up toWordPress 7.0 · core on the reference date: 7.1
Requires WordPress5.5
Requires PHP7.4
Rating4.7 out of 5 from 176 ratings
Support threads, two months4 of 8 marked resolved
Listed since20 Mar 2020
Total downloads1,832,641, updates included
Tags2-factor-authentication, 2fa, google-authenticator, two-factor-authentication, wordpress-authentication

Tags

TagPlugins with 10,000+ installs and this tagRank by installsMedian days since release
2-factor-authentication1117
2fa12416
google-authenticator2116
two-factor-authentication5315
wordpress-authentication1117

Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.

Class of 2020

WP 2FA has been listed since 20 Mar 2020. Of the 150 plugins with 10,000+ installs added in 2020, 87.3% released within the 365 days before the reference date.

Same group, shared tags

Not a recommendation; the same figures for comparison. Alphabetical.

PluginActive installsLast releaseRating
All-In-One Security1,000,000 to 1,999,99915 days before the reference date4.7 (1,715)
Kadence Security700,000 to 799,99932 days before the reference date4.6 (3,990)
Really Simple Security3,000,000 to 3,999,9994 days before the reference date4.9 (8,862)
Two Factor100,000 to 199,999154 days before the reference date4.8 (208)
Wordfence Security5,000,000 to 5,999,99918 days before the reference date4.7 (4,983)

Do you maintain WP 2FA?

If you maintain WP 2FA, you can link to this profile, for example from your readme or your website. Both snippets show this badge:

WP 2FA in the Plugin Directory Census 01/2026

HTML

<a href="https://hafenstudios.com/en/census/plugins/wp-2fa/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="WP 2FA in the Plugin Directory Census 01/2026" width="220" height="40"></a>

Markdown

[![WP 2FA in the Plugin Directory Census 01/2026](https://hafenstudios.com/census/plugins/badge-en.svg)](https://hafenstudios.com/en/census/plugins/wp-2fa/)

The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.

A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.

How to cite

hafenstudios (2026): WP 2FA – Two-factor authentication for WordPress, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/wp-2fa/

Source and status

All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.

Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.