by Patsikov Artem 5 (1 reviews)

Registration Email Blocker

Name: Registration Email Blocker
Rating: 5.0 (1 reviews)
Author: Patsikov Artem

Control which email domains may be used to register on your site and to change an existing account's email address.

Registration Email Blocker ranks #15,607 among WordPress.org plugins with 100+ active installations, is #622 of 3,634 in the Communication category, a 5/5 rating from 1 reviews, and was last updated Sep 9, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.1.0 Current Version v1.1.0

Updated 1 month ago Last Update on 09 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#622 of 3,634 in Communication Top 25% by installs

View on WordPress.org

Rank

#15,607

— No change

Active Installs

100+

— No change

KW Avg Position

0.7 better

Downloads

+2 today

Support Resolved

— No change

Rating

100%

Review 5 out of 5

5 (1 reviews)

Next Milestone 200

Total Progress 32%

100+ 200+

2,933

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 68 more installs to reach 200+

Rank Changes

Current #15,607

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0

1 reviews

Overall 100%

1 (100%)

0 (0%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for Registration Email Blocker. Checked 1 month ago.

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.1.0
Last Updated: Sep 09, 2026
Requires WP: 6.2+
Tested Up To: 7.1.4
PHP Version: 8.0 or higher
Author: Patsikov Artem

Support & Rating

Rating: ★ ★ ★ ★ ★ 5
Reviews: 1
Support Threads: 0
Resolved: 0%

Keywords

email email validation registration spam User Registration

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

WP Mail SMTP by WPForms – SMTP for Reliable Email Delivery with Gmail, Outlook, Amazon SES, Brevo, Other SMTP & More

4M+ installs

#12

MC4WP: Mailchimp for WordPress

1M+ installs

#35

Hostinger Reach – AI-Powered Email Marketing for WordPress

1M+ installs

#41

Popup Builder & Popup Maker for WordPress – OptinMonster Email Marketing and Lead Generation

FluentSMTP – WP Mail SMTP Plugin with Amazon SES, SendGrid, Mailgun, Postmark, Cloudflare, toSend, Gmail and Any SMTP

700K+ installs

#87

Joinchat – Enhanced “click to chat”

700K+ installs

#89

View all Communication plugins

TL;DR

AI summary of the plugin's readme

This plugin is for Russian website owners who need to control which email domains users can register with, including WooCommerce store operators. It restricts registration to approved or blocked email domains to help address the email-related aspect of Federal Law 406-FZ compliance.

Blacklist mode for domains
Whitelist mode for domains
Warning or hard blocking enforcement
Identifies non-compliant existing users
Bulk email change notifications
Detailed registration logging
WooCommerce integration
CSV export of users

Frequently Asked Questions

Common questions about Registration Email Blocker

No. The law requires authorization by phone number, ESIA, a biometric system or another Russian-controlled system, and this plugin implements none of them. It controls email domains only. Consult a lawyer about your actual obligations.

Yes. A blocklist can only refuse domains you have listed, and new mail providers appear constantly. If it matters that only certain providers are used, switch to allowlist mode.

Not retroactively. Existing accounts keep working. They appear in the "Affected users" tab so you can see who is affected and notify them, and if email change checking is enabled they will be asked for a compliant address the next time they edit their profile.

Not while email change checking is on: the rules apply to the account being edited, whoever is doing the editing. Administrators are exempt as accounts, not as editors. To make an exception, either turn the setting off, or use the regiembl_skip_validation filter.

The domain rules do. The reports about existing accounts do not: they rely on SUBSTRING_INDEX, which the SQLite integration does not provide, and the "Affected users" tab will show nobody. This affects development environments such as WordPress Playground, not ordinary MySQL or MariaDB hosting.

Administrators are exempt by default. Leave that setting on unless you have a specific reason to change it.

Yes. The block checkout is validated through the Store API, which requires WooCommerce 9.9 or newer. The classic shortcode checkout is validated as well, on any version.

Nothing, as far as this plugin is concerned. WordPress and WooCommerce already reject malformed addresses with a message that explains the real problem, so the plugin stays out of the way and does not record it as a blocked domain.

Yes. Type it in Cyrillic and it is converted to punycode when you save. If the PHP intl extension is missing on your server, the plugin tells you so and you can enter the punycode form directly, for example xn--80a1acny.xn--p1ai.

Registration checks are a string comparison against a list held in memory, so the cost is negligible. The reports about existing accounts are heavier by nature. They are answered with aggregate SQL rather than by loading user objects, the results are cached for an hour, and the tables are paginated. If you do not need that report on a very large site, turn off "Report existing accounts that do not comply" and it will not be calculated at all.