codicone

The whitelist/blacklist plugin gives you a strong layer of security for your website because not only does the plugin limits unauthorized user access to your site but also creates a log. The log helps to create new blacklist entries. The increase in your blacklist entries means a decrease in spam and security threats. So it is a great safety measure to start with.
It is a very handy plugin that you can add to your WordPress site for added security. It helps you to tailor your preferences about which email addresses you want to allow for registration on your site.
You can create a list of all email addresses or email domains that you wish to receive registrations. On the other hand, you can add a list for blacklist domains to not allow any registration from specific domains. Blacklisting is time-saving because most of the time you have already figured where the spam comes from. So you close those doors already. It is relatively safe also because you are not risking anything prospective.
<h4>Compatible With</h4>
<ul>
<li>WooCommerce</li>
<li>bbpress</li>
<li>buddypress</li>
<li>Profile Builder</li>
<li>WP User Frontend</li>
<li>User Registration</li>
<li>Ultimate member</li>
</ul>

Blacklist & Whitelist Domains for Registration

The whitelist/blacklist plugin gives you a strong layer of security for your website because not only does the plugin limits unauthorized user access  …

nerdismftw.com

Define allowed routes for your website, all other routes will return a 404 error. Permalinks will be overruled.
Login, Backend routes and local files (like wp-login.php) are always available to prevent a lockout.
Also delete all your page caches after enabling to prevent unwanted routing behavior.
Use cases:
<ul>
<li>Absolute control over all permalinks</li>
<li>Prevent unwanted search engine indexing</li>
<li>Be sure no custom post type adds unwanted permalinks</li>
<li>No frontend needed</li>
</ul>
Important:
<ul>
<li>The routing overrules permalinks and works like a whitelist. Only correct entered routes will go through. You should test the routing before using on production environments</li>
<li>Be careful using several routing- or redirect plugins at the same time</li>
<li>Do not forget to delete all your page caches after enabling/disabling the routing to prevent unwanting routing behavior</li>
</ul>
Behaviour:
<ul>
<li>The used protocol (HTTP or HTTPS) will be ignored</li>
<li>GET params will be ignored</li>
<li>Routes are case sensitive</li>
</ul>
Syntax / Wildcards:
<ul>
<li>The route / allows the index page (Check the checkbox \”Allow index page\”)</li>
<li>Wildcard * allows a single term with an arbitrary value (e.g. category//page/)</li>
<li>Wildcard ** permits all possible combinations of terms (e.g. category/**) This wildcard is only allowed at the end of a route</li>
<li>Wildcards are only allowed as complete terms. Correct: /foo//bar/** Wrong: /foo/ba/test**</li>
</ul>

Allowed Routes

Define only allowed routes for your website. Permalinks will be overruled. Wildcard Support.

Blacklist & Whitelist Domains for Registration vs Allowed Routes