SwiftNinjaPro

A Plugin That only allows whitelisted IP’s, or optionally whitelisted browsers, to access wp-login. 
This plugin does Not effect front-end login plugins. 
If an IP is not whitelisted, the wp-login page will be killed and replaced with a message saying “your IP/Browser is not whitelisted”, or optionally redirect the user to 404 page instead.
A better way to hide wp-login. You can add a list of admin IP’s to this plugin, where you want to allow usage of wp-login. 
Even if you have other users that login, its better to use another plugin for a more secure front end login, and this plugin will only allow a specific list of IP’s to access the wp-login page. 
You can also (optionally) have this plugin attempt to redirect anyone to 404 page, if they try and access wp-login without the right IP. 
You can also choose to disable the 404 redirect, and instead tell users there IP is not whitelisted, and that they should contact the admin if this is in error. 
The plugin does Not block wp-admin, so once logged in, you can still edit your site on the go. 
The plugin also has an option to whitelist your favorite common browsers to wp-login. This means you can keep users from accessing the wp-login page, simply because there using Internet Explore, and not what you chose to allow. 
There is another option (which may return false positives), that attempts to check if the source of an IP is commonly used by a proxy server, and can block proxy IP’s to try and reduce spoofing.

WP-Login and WP-Admin Whitelist

A Plugin That only allows whitelisted IP's, or optionally whitelisted browsers, to access wp-login, or optionally wp-admin.

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.

WP-Login and WP-Admin Whitelist vs Allowed Routes