Title: IP Location Block
Author: Darko G.
Published: <strong>Me 17, 2021</strong>
Last modified: Mas 13, 2026

---

Search plugins

![](https://ps.w.org/ip-location-block/assets/banner-772x250.png?rev=2662027)

![](https://ps.w.org/ip-location-block/assets/icon-256x256.png?rev=2662027)

# IP Location Block

 By [Darko G.](https://profiles.wordpress.org/darkog/)

[Download](https://downloads.wordpress.org/plugin/ip-location-block.1.3.8.zip)

 * [Details](https://hat.wordpress.org/plugins/ip-location-block/#description)
 * [Reviews](https://hat.wordpress.org/plugins/ip-location-block/#reviews)
 *  [Installation](https://hat.wordpress.org/plugins/ip-location-block/#installation)
 * [Development](https://hat.wordpress.org/plugins/ip-location-block/#developers)

 [Support](https://wordpress.org/support/plugin/ip-location-block/)

## Description

IP Location Block plugin that allows you to block access to your site based on the
visitor location while also keeping your site safe from malicious attacks. The plugin
brings a smart and powerful protection methods such as “**WP Metadata Exploit Protection**“.

Combined with those methods and IP address geolocation, you’ll be surprised to find
a bunch of malicious or undesirable access blocked in the logs of this plugin after
several days of installation.

**Note:** This plugin is based on the now abandoned “IP Geo Block” plugin by tokkonopapa.
I fixed various issues and improved the overall codebase.

#### Features

 * **Native Geo-Location Provider**
    IP Location Block provides [Native Geo-Location Provider](https://iplocationblock.com/codex/native-geo-location-provider/?utm_source=plugin&utm_medium=wporgpage&utm_campaign=readme)
   that is faster, more secure and provides the needed **precision** for matching**
   CITY** and **STATE** besides the standard COUNTRY matching.
 * **Privacy by design:**
    IP address is always encrypted on recording in logs/cache.
   Moreover, it can be anonymized and restricted on sending to the 3rd parties such
   as geolocation APIs or whois service.
 * **Immigration control:**
    Access to the basic and important entrances into back-
   end such as `wp-comments-post.php`, `xmlrpc.php`, `wp-login.php`, `wp-signup.
   php`, `wp-admin/admin.php`, `wp-admin/admin-ajax.php`, `wp-admin/admin-post.php`
   will be validated by means of a country code based on IP address. It allows you
   to configure either whitelist or blacklist to [specify the countires](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements),
   [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing)
   for a range of IP addresses and [AS number](https://en.wikipedia.org/wiki/Autonomous_system_(Internet))
   for a group of IP networks.
 * **Guard against login attempts:**
    In order to prevent hacking through the login
   form and XML-RPC by brute-force and the reverse-brute-force attacks, the number
   of login attempts will be limited per IP address even from the permitted countries.
 * **Minimize server load against brute-force attacks:**
    You can configure this
   plugin as a [Must Use Plugins](https://codex.wordpress.org/Must_Use_Plugins) 
   so that this plugin can be loaded prior to regular plugins. It can massively 
   [reduce the load on server](https://iplocationblock.com/codex/validation-timing/).
 * **Prevent malicious down/uploading:**
    A malicious request such as exposing `
   wp-config.php` or uploading malwares via vulnerable plugins/themes can be blocked.
 * **Block badly-behaved bots and crawlers:**
    A simple logic may help to reduce
   the number of rogue bots and crawlers scraping your site.
 * **Support of BuddyPress and bbPress:**
    You can configure this plugin so that
   a registered user can login as a membership from anywhere, while a request such
   as a new user registration, lost password, creating a new topic and subscribing
   comment can be blocked by country. It is suitable for [BuddyPress](https://wordpress.org/plugins/buddypress/)
   and [bbPress](https://wordpress.org/plugins/bbpress/) to help reducing spams.
 * **Referrer suppressor for external links:**
    When you click an external hyperlink
   on admin screens, http referrer will be eliminated to hide a footprint of your
   site.
 * **Multiple source of IP Geolocation databases:**
    Besides the [Native Geo-Location provider](https://iplocationblock.com/codex/native-geo-location-provider/?utm_source=plugin&utm_medium=wporgpage&utm_campaign=readme),
   this plugin supports [MaxMind GeoLite2 free databases](https://www.maxmind.com)
   and [IP2Location LITE databases](https://www.ip2location.com/). Also free Geolocation
   REST APIs and whois information can be available for audit purposes. Father more,
   [dedicated API class libraries](https://iplocationblock.com/cloudflare-cloudfront-api-class-library/)
   can be installed for CloudFlare and CloudFront as a reverse proxy service.
 * **Customizing response:**
    HTTP response code can be selectable as `403 Forbidden`
   to deny access pages, `404 Not Found` to hide pages or even `200 OK` to redirect
   to the top page. You can also have a human friendly page (like `404.php`) in 
   your parent/child theme template directory to fit your site design.
 * **Validation logs:**
    Validation logs for useful information to audit attack 
   patterns can be manageable.
 * **Cooperation with full spec security plugin:**
    This plugin is lite enough to
   be able to cooperate with other full spec security plugin such as [Wordfence Security](https://wordpress.org/plugins/wordfence/).
   See [this report](https://iplocationblock.com/codex/page-speed-performance/) 
   about page speed performance.
 * **Extendability:**
    You can customize the behavior of this plugin via `add_filter()`
   with [pre-defined filter hook](https://iplocationblock.com/codex/). See various
   use cases in [samples.php](https://iplocationblock.com/codex/example-use-cases-for-the-developer-hooks/)
   bundled within this package. You can also get the extension [IP Geo Allow](https://github.com/ddur/WordPress-IP-Geo-Allow)
   by [Dragan](https://github.com/ddur). It makes admin screens strictly private
   with more flexible way than specifying IP addresses.
 * **Self blocking prevention and easy rescue:**
    Website owners do not prefer themselves
   to be blocked. This plugin prevents such a sad thing unless you force it. And
   futhermore, if such a situation occurs, you can [rescue yourself](https://iplocationblock.com/codex/what-should-i-do-when-im-locked-out/)
   easily.
 * **Clean uninstallation:**
    Nothing is left in your precious mySQL database after
   uninstallation. So you can feel free to install and activate to make a trial 
   of this plugin’s functionality.

#### Documentation

Documentation and more information can always be found on our [plugin website](https://iplocationblock.com/).

#### Attribution

This package includes GeoLite2 library distributed by MaxMind, available from [MaxMind](https://www.maxmind.com),
and also includes IP2Location open source libraries available from [IP2Location](https://www.ip2location.com).

Also thanks for providing the following services and REST APIs for free.

 * [http://geoiplookup.net/](http://geoiplookup.net/) (IPv4, IPv6 / free)
 * [https://ipinfo.io/](https://ipinfo.io/) (IPv4, IPv6 / free)
 * [https://ipapi.com/](https://ipapi.com/) (IPv4, IPv6 / free, need API key)
 * [https://ipstack.com/](https://ipstack.com/) (IPv4, IPv6 / free, need API key)
 * [https://ipinfodb.com/](https://ipinfodb.com/) (IPv4, IPv6 / free, need API key)

#### Development

Development of this plugin happens at [IP Location Block – GitHub](https://github.com/gdarko/ip-location-block)

All contributions will always be welcome.

#### Known issues

 * From [WordPress 4.5](https://make.wordpress.org/core/2016/03/09/comment-changes-in-wordpress-4-5/),`
   rel=nofollow` had no longer be attached to the links in `comment_content`. This
   change prevents to block “[Server Side Request Forgeries](https://www.owasp.org/index.php/Server_Side_Request_Forgery)”(
   not Cross Site but a malicious internal link in the comment field).
 * [WordPress.com Mobile App](https://apps.wordpress.com/mobile/) can’t execute 
   image uploading because of its own authentication system via XMLRPC.

## Screenshots

 * [[
 * **IP Location Plugin** – Settings tab
 * [[
 * **IP Location Plugin** – Validation rules and behavior
 * [[
 * **IP Location Plugin** – Back-end target settings
 * [[
 * **IP Location Plugin** – Front-end target settings
 * [[
 * **IP Location Plugin** – Geolocation API settings
 * [[
 * **IP Location Plugin** – IP address cache settings
 * [[
 * **IP Location Plugin** – Statistics tab
 * [[
 * **IP Location Plugin** – Logs tab
 * [[
 * **IP Location Plugin** – Search tab
 * [[
 * **IP Location Plugin** – Attribution tab

## Installation

#### Using The WordPress Dashboard

 1. Navigate to the ‘Add New’ in the plugins dashboard
 2. Search for ‘IP Location Block’
 3. Click ‘Install Now’
 4. Activate the plugin on the Plugin dashboard
 5. Stay cool for a while and go to ‘Settings’ » ‘IP Location Block’
 6. Try ‘Best for Back-end’ button for easy setup at the bottom of this plugin’s setting
    page.

Please refer to [the document](https://iplocationblock.com/codex/) for your best
setup.

## FAQ

### Does the site using this plugin comply with GDPR?

This plugin is designed based on the principle of “Privacy by design” so that you
can compliantly run it to GDPR. As guarding against personal data breach, IP addresses
in this plugin are encrypted and also can be anonymized by default. It also provides
some functions not only to manually erase them but also to automatically remove 
them when those are exceeded a certain amount/time.

However, these are the part of GDPR requirements and do not guarantee that the site
is compliant with GDPR. Refer to [3.0.11 release note](https://iplocationblock.com/changelog/0-3-0-11-release-note/)
for details.

### Is there a way to migrate from IP Geo Block”

Yes, if “IP Geo Block” settings are detected, you will see migrate option in the
Settings last in “Plugin Settings” section. This will copy the settings from “IP
Geo Block” only.

### Does this plugin support multisite?

Yes. You can synchronize the settings with all the sites on the network when you
activate on network and enable “**Network wide settings**” in “**Plugin settings**”
section.

### Does this plugin allows blocking US States, Country Regions or Cities?

Yes. Please view [City/State Level Matching](https://iplocationblock.com/codex/city-state-level-matching/)
for more details.

### Does this plugin works well with caching?

The short answer is **YES**, especially for the purpose of security e.g. blocking
malicious access both on the back-end and on the front-end.

You can find the long answer and the compatibility list of cache plugins at “[Compatibility with cache plugins](https://iplocationblock.com/codex/compatibility-with-cache-plugins/)“.

### I still have access from blacklisted country. Does it work correctly?

Absolutely, YES.

Sometimes, a WordFence Security user would report this type of claim when he/she
found some accesses in its Live traffic view. But please don’t worry. Before WordPress
runs, WordFence cleverly filters out malicious requests to your site using [auto_prepend_file](https://php.net/manual/en/ini.core.php#ini.auto-prepend-file)
directive to include PHP based Web Application Firewall. Then this plugin validates
the rest of the requests that pass over Wordfence because those were not in WAF 
rules.

It would also possibly be caused by the accuracy of country code in the geolocation
databases. Actually, there is a case that a same IP address has different country
code.

For more detail, please refer to “[I still have access from blacklisted country.](https://iplocationblock.com/codex/i-still-have-access-from-blacklisted-country/)“.

### How can I test this plugin works?

The easiest way is to use [free proxy browser addon](https://www.google.com/search?q=free+proxy+browser+addon).

Another one is to use [http header browser addon](https://www.google.com/search?q=browser+add+on+modify+http+header).

You can add an IP address to the `X-Forwarded-For` header to emulate the access 
behind the proxy. In this case, you should add `HTTP_X_FORWARDED_FOR` into the “**
$_SERVER keys for extra IPs**” on “**Settings**” tab.

See more details at “[How to test prevention of attacks](https://iplocationblock.com/?codex-category=test-prevention-of-attacks)“.

### I’m locked out! What shall I do?

Please find the solution in [Quick recovery from blocking on your login page](https://iplocationblock.com/codex/quick-recovery-from-blocking-on-login-page/)
at first.

You can also find another solution by editing “**Emergent Functionality**” code 
section near the bottom of `ip-location-block.php`. This code block can be activated
by replacing `/*` (opening multi-line comment) at the top of the line to `//` (single
line comment), or `*` at the end of the line to `*/` (closing multi-line comment).

    ```
    /**
     * Invalidate blocking behavior in case yourself is locked out.
     *
     * How to use: Activate the following code and upload this file via FTP.
     */
    /* -- ADD '/' TO THE TOP OR END OF THIS LINE TO ACTIVATE THE FOLLOWINGS -- */
    function ip_location_block_emergency( $validate, $settings ) {
        $validate['result'] = 'passed';
        return $validate;
    }
    add_filter( 'ip-location-block-login', 'ip_location_block_emergency', 1, 2 );
    add_filter( 'ip-location-block-admin', 'ip_location_block_emergency', 1, 2 );
    // */
    ```

Please not that you have to use an [appropriate editor](https://codex.wordpress.org/Editing_Files#Using_Text_Editors).

After saving and uploading it to `/wp-content/plugins/ip-location-block/` on your
server via FTP, you become to be able to login again as an admin.

Remember that you should upload the original one after re-configuration to deactivate
this feature.

[This document](https://iplocationblock.com/codex/what-should-i-do-when-im-locked-out/)
can also help you.

### Do I have to turn on all the selection to enhance security?

Yes. Roughly speaking, the strategy of this plugin has been constructed as follows:

 * **Block by country**
    It blocks malicious requests from outside your country.
 * **Force to load WP core**
    It blocks the request which has not been covered in
   the above two.
 * **Bad signatures in query**
    It blocks the request which has not been covered
   in the above three.

Please try “**Best for Back-end**” button at the bottom of this plugin’s setting
page for easy setup. And also see more details in “[The best practice of target settings](https://iplocationblock.com/codex/the-best-practice-for-target-settings/)“.

### Does this plugin validate all the requests?

Unfortunately, no. This plugin can’t handle the requests that are not parsed by 
WordPress. In other words, a standalone file (PHP, CGI or something executable) 
that is unrelated to WordPress can’t be validated by this plugin even if it is in
the WordPress install directory.

But there’s exceptions: When you enable “**Force to load WP core**” for **Plugins
area** or **Themes area**, a standalone PHP file becomes to be able to be blocked.
Sometimes this kind of file has some vulnerabilities. This function protects your
site against such a case.

### How to resolve “Sorry, your request cannot be accepted.”?

If you encounter this message, please refer to [this document](https://iplocationblock.com/codex/why-sorry-your-request-cannot-be-accepted/)
to resolve your blocking issue.

If you can’t solve your issue, please let me know about it on the [support forum](https://wordpress.org/support/plugin/ip-location-block/).
Your logs in this plugin and “**Installation information**” at “**Plugin settings**”
will be a great help to resolve the issue.

### How to resolve issues related to ajax-requests being blocked in admin?

Check the “Admin ajax/post” option in “Back-end target settings”, either disable
it or whitelist the required Ajax actions.

### How can I fix “Unable to write” error?

When you enable “**Force to load WP core**” options, this plugin will try to configure`.
htaccess` in your `/wp-content/plugins/` and `/wp-content/themes/` directory in 
order to protect your site against the malicious attacks to the [OMG plugins and themes](https://iplocationblock.com/prevent-exposure-of-wp-config-php/).

But some servers doesn’t give read / write permission against `.htaccess` to WordPress.
In this case, you can configure `.htaccess` files by your own hand instead of enabling“**
Force to load WP core**” options.

Please refer to “[How can I fix permission troubles?](https://iplocationblock.com/codex/how-can-i-fix-permission-troubles/)”
in order to fix this error.

## Reviews

![](https://secure.gravatar.com/avatar/85d451b90c2941ec0f0e5b3ed4c742fcd6ec81a4d462c372bc55730c94424d69?
s=60&d=retro&r=g)

### 󠀁[Great plugin does what it promises!](https://wordpress.org/support/topic/great-plugin-does-what-it-promises-8/)󠁿

 [tom4all](https://profiles.wordpress.org/tom4all/) Mas 3, 2026 1 reply

Works as promised, I just have a few problems with the nonce…

![](https://secure.gravatar.com/avatar/b5984c71ee92161583ead3ea7fbb4ba730829b063b84b40228e9b09a5a64a3ce?
s=60&d=retro&r=g)

### 󠀁[Exactly What I Needed for GEO Blocking!](https://wordpress.org/support/topic/exactly-what-i-needed-for-geo-blocking/)󠁿

 [dmac](https://profiles.wordpress.org/darrenmcentee/) Septanm 2, 2025

This plugin is a lifesaver for managing access by location. Setup was quick and 
straightforward, and it’s been working perfectly right out of the box. Since installing
it, I’ve noticed a significant decrease in suspicious login attempts. If you want
an easy, reliable way to block visitors from certain countries, this is an excellent
choice. A practical and well-built plugin!

![](https://secure.gravatar.com/avatar/0da3896e414717428fa3f0eb0d728282c2b2ab5c2a6d05e773949b1282463864?
s=60&d=retro&r=g)

### 󠀁[funciona força bé i redueix trànsit innecessari](https://wordpress.org/support/topic/funciona-forca-be-i-redueix-transit-innecessari/)󠁿

 [ibosch](https://profiles.wordpress.org/ibosch/) Jen 13, 2025

S’ha de ficar com a “mu” a les opcions per a tallar el trànsit que no es vol.Si 
el teu target de clients està al Chunguetistan, pots fer una white list de chunguetistan,
la teva IP de gestió i la IP del servidor. D’aquesta manera evites els centenars
d’atacs continuats que rebia des de EEUU, Alemanya, Irlanda, França, … i ara gràcies
a aquest plugin només rebo visites dels meus clients, que estan a Chunguetistan.
0 bots o crawlers, només visites reals i ventes!gràcies!

![](https://secure.gravatar.com/avatar/60374d9a4a1c1edd4cba9ca6978fa573e552cd2619b293f83fe1525e5ca0168f?
s=60&d=retro&r=g)

### 󠀁[Doesn’t Work](https://wordpress.org/support/topic/doesnt-work-3221/)󠁿

 [thebuilder](https://profiles.wordpress.org/cway/) Jen 3, 2025 1 reply

It doesn’t seem to work. Under Settings, in the Matching Rule, Whitelist is selected
and it says ‘A request from which the country code or IP address is NOT in the whitelist
will be blocked.’ I’ve added my state US:State:Colorado. When spam is submitted,
I looked-up their IP address and saw they were from Florida. In the Blacklist matching
rule, I added US:State:Florida, and I still get spam from Florida.

![](https://secure.gravatar.com/avatar/10047079c89673e5badf96515fdafead2d17c1be7145b935b403a8bbe5675528?
s=60&d=retro&r=g)

### 󠀁[⭐⭐⭐⭐⭐ Perfect for Country-Based Blocking!](https://wordpress.org/support/topic/%e2%ad%90%e2%ad%90%e2%ad%90%e2%ad%90%e2%ad%90-perfect-for-country-based-blocking/)󠁿

 [arultamilnadu](https://profiles.wordpress.org/arultamilnadu/) Mas 5, 2025

This plugin does exactly what I needed—blocks traffic from specific countries without
any hassle. Super easy to set up, and it works flawlessly. I’ve seen a big drop 
in unwanted login attempts since installing it. If you’re looking for a simple and
effective way to control access by location, this is the one to go for. Huge thanks
to the developer, Darko G., for creating such a useful plugin! I am From India, 
Tamilnadu.

![](https://secure.gravatar.com/avatar/04dc7d33d52e6fab62a5bc1a264bb1e9931cdcb5114bb47d79bfa5dcf8d4d678?
s=60&d=retro&r=g)

### 󠀁[Good Geoblocking Tool](https://wordpress.org/support/topic/good-geoblocking-tool/)󠁿

 [allbutone](https://profiles.wordpress.org/allbutone/) Janvye 17, 2025

I am using this plugin to block all countries from the backend (except my own of
course) and to redirect foreign visitors (bots) from my contact page with a form
to another contact page without a form (to prevent spam). This all works very well!
The disadvantage is that the UI is rather poor and difficult to navigate. Thank 
you for the plugin!

 [ Read all 33 reviews ](https://wordpress.org/support/plugin/ip-location-block/reviews/)

## Contributors & Developers

“IP Location Block” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ Darko G. ](https://profiles.wordpress.org/darkog/)

“IP Location Block” has been translated into 2 locales. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/ip-location-block/contributors)
for their contributions.

[Translate “IP Location Block” into your language.](https://translate.wordpress.org/projects/wp-plugins/ip-location-block)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/ip-location-block/),
check out the [SVN repository](https://plugins.svn.wordpress.org/ip-location-block/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/ip-location-block/)
by [RSS](https://plugins.trac.wordpress.org/log/ip-location-block/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.3.8

_Release Date – 13 Mar 2026_

 * Fix: PHP Warnings
 * Fix: Deprecated jQuery calls
 * Add: Kinsta/WPEngine
 * Deprecate WP-ZEP (Zero-Day Prevention) to be removed in 1.4.0
 * Test with WordPress 7.0

#### 1.3.7

_Release Date – 07 Nov 2025_

 * New: Add instructions to migrate to latest IP Location Block platform
 * New: Test with latest WordPress

#### 1.3.6

_Release Date – 06 Aug 2025_

 * Fix: Uncaught ReferenceError: IP_LOCATION_BLOCK_AUTH is not defined
 * Fix: IP_Location_Block::is_user_logged_in() in certain cases
 * Fix: Plugins run if HASH constants are not defined

#### 1.3.5

_Release Date – 20 Jul 2025_

 * Fix PHP warnings related to string translation
 * Fix PHP Fatal error related to undefined constants (eg. NONCE_KEY)

#### 1.3.4

_Release Date – 07 Mar 2025_

 * Fix PHP warnings
 * Test with PHP 8.4
 * Test with WordPress 6.7 and 6.8-beta1

#### 1.3.3

_Release Date – 24 Sep 2024_

 * Fix admin post/ajax whitelisting
 * Fix PHP deprecation warnings
 * Fix PHP array access warnings
 * Fix support for Divi
 * Whitelist additional WordPress ajax actions by default
 * Remove unnecessary/unused files within the maxmind php extension

#### 1.3.2

_Release Date – 01 Aug 2024_

 * Fix deprecation warning in PHP 8.2+
 * Test with WordPress 6.6

#### 1.3.1

_Release Date – 03 Apr 2024_

 * Drop GeoIPLookup API because – the service ceased operations.
 * Test with WordPress 6.5

#### 1.3.0

_Release Date – 20 Feb 2024_

 * Fix issue when “Front-end rules & behavior” matching rule is blacklist, response
   status is 30X and redirect URL is empty. It does not redirect.
 * Set the default blacklist redirect URL to blocked.iplocationblock.com.
 * Add status box in the settings screens that tells account quota, current running
   mode, etc.
 * Improve wording at few places that caused confusion.

#### 1.2.3

_Release Date – 12 Nov 2023_

 * Prefix the css code to fix conflicts with other plugins (Woo / Super Cache, etc)
 * Add more sophisticated warnings when blocking rules are misconfigured or ASN 
   is in use but the current enabled providers does not support ASN.
 * Exclude Divi “save-epanel” ajax action from ZEP
 * Fix warning triggered by the cron script

#### 1.2.2

_Release Date – 01 Nov 2023_

 * Fix issue related to log and stats display
 * Fix issue that triggered alert on non-admin users (Editor and other)
 * Add additional two columns for CITY and STATE to Logs screen when using “IP Location
   Block” provider
 * Fix warnings when downloading Geolite2 DB
 * Other UI Improvements
 * Various Codebase improvements

#### 1.2.1

_Release Date – 31 Oct 2023_

 * Fix SQLite logging related errors

#### 1.2.0

_Release Date – 30 Oct 2023_

 * Precision blocking by city/state support via the native IP Location Block provider
 * Fixes various PHP 8.2 warnings reported on Github & forums
 * Codebase improvements related to external API providers
 * Test with WordPress 6.4

#### 1.1.5

_Release Date – 28 May 2023_

 * Deploy procedure hotfix

#### 1.1.4

_Release Date – 28 May 2023_

 * Codebase improvements
 * Drop the IP-API.com for now until we refactor the settings and make it possible
   to support apis that can be used with and without key.
 * Fix array to string conversion when using the IPInfoDB provider
 * Refactor the search tab backend procedure

#### 1.1.3

_Release Date – 24 Jul 2022_

 * Re-write the download_zip procedure to improve the external ip database download
 * Improved logged-in user detection when validation timing is enabled, fixes blocking
   issues in admin, undefined constants, etc.
 * Disable restrict_api by default so the external APIs will be enabled by default

#### 1.1.2

_Release Date – 03 May 2022_

 * Fix issues with downloading local databases

#### 1.1.1

_Release Date – 02 May 2022_

 * Fix fatal error caused by removed constant still in use

#### 1.1.0

_Release Date – 01 May 2022_

 * Introducing premium [IP Location Block REST API](https://iplocationblock.com/introducing-geolocation-api/)
 * Introduced new design for the provider table in Settings
 * Make action and filter names readable by IDEs
 * Fix a bug that prevented uninstalling the plugin
 * Fix various warnings triggered in PHP8+

#### 1.0.7

_Release Date – 21 Dec 2021_

 * Fix IPv6.php – add compatibility with PHP7.4+

#### 1.0.6

_Release Date – 21 Nov 2021_

 * Fixes broken plugin admin settings / stats pages

#### 1.0.5

_Release Date – 20 Nov 2021_

 * Fix 307 Response Redirect loop
 * Fix wrong cron info in admin settings
 * Fix Undefined array key warnings in PHP8
 * FIx undefined IP_LOCATION_BLOCK_AUTH in some environments.

#### 1.0.4

_Release Date – 08 Jun 2021_

 * Fix bugs related to the asn blocking feature
 * Trigger re-download of the asn database once the ASN feature is enabled via settings
 * Improved migration from legacy process, unset unused settings

#### 1.0.3

_Release Date – 18 May 2021_

 * Add “Migrate from IP Geo Block” option if IP Geo Block settings are detected.
   This will copy the IP Geo Block settings.
 * Replaced the deprecated jQuery.trim() calls with String.trim()
 * Fix error when deleting the Emergency link using the “Delete current link” button.

#### 1.0.2

_Release Date – 18 May 2021_

 * Fix mu-plugins option

#### 1.0.1

_Release Date – 17 May 2021_

 * Drop ipdata.co API
 * Fixed the search tool

#### 1.0.0

_Release Date – 17 May 2021_

 * Added PHP8 compatibility
 * Added support for Maxmind GeoLite2 database with api key
 * Replaced Google Maps with OSM/Leaflet
 * Updated DNS2 Library to support PHP8
 * Fixed IP2Location provider errors. Update to the latest version
 * Fixed various errors caught in error logs triggered in the newer PHP versions
 * Fixed the ipinfo.io API
 * Fixed the ipdata.co API

## Meta

 *  Version **1.3.8**
 *  Last updated **3 weeks ago**
 *  Active installations **10,000+**
 *  WordPress version ** 3.7 or higher **
 *  Tested up to **7.0**
 *  Languages
 * [English (US)](https://wordpress.org/plugins/ip-location-block/), [Japanese](https://ja.wordpress.org/plugins/ip-location-block/),
   and [Spanish (Spain)](https://es.wordpress.org/plugins/ip-location-block/).
 *  [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/ip-location-block)
 * Tags
 * [block](https://hat.wordpress.org/plugins/tags/block/)[country](https://hat.wordpress.org/plugins/tags/country/)
   [geolocation](https://hat.wordpress.org/plugins/tags/geolocation/)[ip address](https://hat.wordpress.org/plugins/tags/ip-address/)
 *  [Advanced View](https://hat.wordpress.org/plugins/ip-location-block/advanced/)

## Ratings

 4.6 out of 5 stars.

 *  [  28 5-star reviews     ](https://wordpress.org/support/plugin/ip-location-block/reviews/?filter=5)
 *  [  2 4-star reviews     ](https://wordpress.org/support/plugin/ip-location-block/reviews/?filter=4)
 *  [  0 3-star reviews     ](https://wordpress.org/support/plugin/ip-location-block/reviews/?filter=3)
 *  [  1 2-star review     ](https://wordpress.org/support/plugin/ip-location-block/reviews/?filter=2)
 *  [  2 1-star reviews     ](https://wordpress.org/support/plugin/ip-location-block/reviews/?filter=1)

[Add my review](https://wordpress.org/support/plugin/ip-location-block/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/ip-location-block/reviews/)

## Contributors

 *   [ Darko G. ](https://profiles.wordpress.org/darkog/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/ip-location-block/)