Nginx IP Geolocation Module for IPGeolocation.io

Overview

Add country, city, ASN, abuse contact, company, and VPN, proxy and Tor detection data to Nginx as native variables, powered by IPGeolocation.io MMDB databases. This Nginx IP geolocation module reads any IPGeolocation.io DBs ( .mmdb ) file directly from disk and exposes the data as $ip_* variables you can use anywhere in your nginx.conf , with no API calls, no network latency, and no per-request cost.

Use it to block anonymous traffic, redirect visitors by country, enforce geo-blocking and compliance rules, personalize content, and enrich your access logs, all at the edge before requests ever reach your application.

# Block Tor exit nodes and known attackers, redirect EU visitors, all at the edge
if ($ip_is_tor) { return 403; }
if ($ip_is_known_attacker) { return 403; }
if ($ip_country_code = DE) { return 302 https://de.example.com$request_uri; }

Why use this module

Most teams reach for IP intelligence in one of two ways: calling a remote API on every request, or wiring a geolocation library into their application code. Both add latency, cost, and complexity. This module takes a third path. It loads IPGeolocation.io databases into Nginx memory once at startup and answers every lookup locally in microseconds.

• No API calls and no per-request billing. Lookups happen in process against a memory-mapped file. There is no outbound request, so there is nothing to rate limit and nothing to pay per lookup.
• Decisions at the edge. Block, redirect, or route traffic in nginx.conf before it reaches your backend. Your application never has to know the visitor's country or risk level unless you choose to forward it as request headers.
• Load only what you need. Point the module at a single database or at several. If you load only a Security database, only the security variables resolve. Load a full bundle and everything resolves. You pay in memory only for the data you actually use.
• One module, many databases. IP Location, IP Security, IP Company, IP to ASN, and IP Abuse Contact databases all work through the same directive and the same variable names.
• Schema resilient. Each variable knows several candidate field paths. The current nested IPGeolocation.io schema is tried first, the older flat schema second, so the same configuration keeps working across database versions.

How it works

You load one or more .mmdb files with the ipgeolocation_db directive. The module opens each file at startup and keeps it memory mapped for the life of the worker process.

When Nginx evaluates an $ip_* variable during a request, the module:

1. Resolves the client IP address (see how the client IP is selected).
2. Looks that IP up in each loaded database, in the order you declared them.
3. Returns the first database that contains the requested field. This is why loading order is also priority order.
4. If no loaded database has the field, the variable resolves to an empty value.

Because the first match wins, you can layer databases. For example, load a Geolocation database and a Security database together, and $ip_country_name resolves from the first while $ip_is_vpn resolves from the second, automatically.

Requirements

• Nginx source that matches the binary you intend to run. This module is compiled into Nginx, so you build Nginx with the module attached.
• libmaxminddb development headers and library. This is the official MMDB reader that the module links against.
• A C compiler toolchain ( gcc or clang , make ).
• At least one IPGeolocation.io .mmdb database file. See which databases provide which variables.

Install libmaxminddb on common systems:

# Debian and Ubuntu
sudo apt-get update
sudo apt-get install -y libmaxminddb0 libmaxminddb-dev mmdb-bin

# RHEL, CentOS, Rocky, Alma (EPEL)
sudo yum install -y libmaxminddb libmaxminddb-devel

# macOS (Homebrew)
brew install libmaxminddb

The mmdbio package provided by IPGeolocation.io is handy for inspecting a database and confirming which fields it contains.

Quick start

Add the module configuration to the http block of your nginx.conf :

http {
    # Load one or more IPGeolocation.io databases. Declaration order is priority order.
    ipgeolocation_db /etc/nginx/ipgeo/db-ip-geolocation.mmdb;
    ipgeolocation_db /etc/nginx/ipgeo/db-ip-security.mmdb;

    # Nginx faces the internet directly, so geolocate the real peer address
    ipgeolocation_trust_forwarded_header off;

    server {
        listen 80;
        server_name example.com;

        location / {
            # Pass enrichment to your backend as request headers
            proxy_set_header X-Geo-Country      $ip_country_code;
            proxy_set_header X-Geo-City         $ip_city_name;
            proxy_set_header X-Geo-Threat-Score $ip_threat_score;
            proxy_pass http://backend;
        }
    }
}

That is the whole setup. Every variable in the full $ip_* variable reference is now available. If Nginx runs behind a load balancer, read how to select the correct client IP before going live.

Testing your configuration

Add a debug endpoint that prints the resolved values, restricted to internal addresses:

# In the http block. Later examples reuse $is_internal.
geo $is_internal {
    default         0;
    127.0.0.1/32    1;
    ::1/128         1;
    10.0.0.0/8      1;
    172.16.0.0/12   1;
    192.168.0.0/16  1;
}

server {
    location = /debug/ipgeo {
        # `return` runs before allow/deny, so gate it with a variable instead
        if ($is_internal = 0) { return 403; }

        default_type text/plain;
        return 200 "country=$ip_country_code city=$ip_city_name asn=$ip_asn vpn=$ip_is_vpn tor=$ip_is_tor threat=$ip_threat_score\n";
    }
}

With ipgeolocation_trust_forwarded_header on , you can simulate any visitor from the server itself:

curl -H "X-Forwarded-For: 2.56.188.34" http://127.0.0.1/debug/ipgeo

Cross-check the output against the raw database record with mmdbio read --db <db> --ip 2.56.188.34 .

Variable reference

Every variable below resolves only if a database you loaded contains the matching field. Variables backed by a database you did not load simply return an empty value, so it is safe to reference any of them. See how booleans, lists, and empty values are formatted.

Real world examples

The snippets below assume the relevant database is loaded in your http block (see where to download each database). map , geo , limit_req_zone , and log_format belong in the http block; if and return go inside server or location . Mix and match them freely.

Using if only to return a response is safe. For anything more complex, compute a flag with map and test that flag, as the examples below do.

# Requires the IP Security database
map "$ip_is_tor$ip_is_known_attacker" $block_anon {
    default 0;
    "~1"    1;   # block if either flag is set
}

map $ip_threat_score $high_risk {
    default                  0;
    "~^(8[0-9]|9[0-9]|100)$" 1;   # threat score 80 to 100
}

server {
    location /login {
        if ($block_anon) { return 403; }
        if ($high_risk)  { return 429; }

        proxy_pass http://app;
    }
}

# Requires the IP Geolocation database
map $ip_country_code $regional_host {
    default  www.example.com;
    DE       de.example.com;
    FR       fr.example.com;
    JP       jp.example.com;
}

# Only the global site redirects, so regional sites can never loop
server {
    server_name www.example.com;

    location / {
        if ($regional_host != $host) {
            return 302 https://$regional_host$request_uri;
        }

        # Or pass locale hints to your app instead of redirecting
        proxy_set_header X-Geo-Country  $ip_country_code;
        proxy_set_header X-Geo-Currency $ip_currency_code;
        proxy_pass http://app;
    }
}

# Requires the IP Geolocation database
map "$is_internal:$ip_country_code" $country_allowed {
    default        0;
    "~^1:"         1;   # private and internal addresses have no country
    "~:(US|CA)$"   1;   # allowed countries
}

server {
    location / {
        if ($country_allowed = 0) { return 451; }   # 451: Unavailable For Legal Reasons
        proxy_pass http://app;
    }
}

# Requires the IP Security database (cloud flag) or the IP to ASN database (ASN type)
map "$ip_is_cloud_provider$ip_asn_type" $is_infra {
    default     0;
    "~1"        1;   # cloud provider flag set
    "~HOSTING"  1;   # ASN classified as hosting
}

# Human traffic gets an empty key, and requests with an empty key are not limited
map $is_infra $infra_limit_key {
    0  "";
    1  $binary_remote_addr;
}

limit_req_zone $infra_limit_key zone=infra:10m rate=30r/m;

server {
    location /api/ {
        limit_req zone=infra burst=10 nodelay;
        proxy_set_header X-Is-Infra $is_infra;
        proxy_pass http://api;
    }
}

log_format geo_json escape=json '{'
    '"time":"$time_iso8601","ip":"$remote_addr","request":"$request","status":"$status",'
    '"country":"$ip_country_code","city":"$ip_city_name",'
    '"asn":"$ip_asn","org":"$ip_asn_organization",'
    '"vpn":"$ip_is_vpn","proxy":"$ip_is_proxy","tor":"$ip_is_tor",'
    '"threat":"$ip_threat_score"}';

server {
    access_log /var/log/nginx/access.geo.log geo_json;
}

# Requires the IP Abuse Contact database
location = /debug/abuse {
    if ($is_internal = 0) { return 403; }

    default_type application/json;
    return 200 '{"ip_route":"$ip_abuse_route","abuse_email":"$ip_abuse_email","abuse_phone":"$ip_abuse_phone","country":"$ip_abuse_country_code"}';
}

How values are formatted

• Booleans become 1 or 0 . Whether the database stores a true boolean or the strings "true" and "false" , the module normalizes both to 1 and 0 . This means $ip_is_vpn , $ip_is_tor , and the other flags work directly in if tests and map blocks.
• Lists are joined with ", " . Array fields such as proxy and VPN provider names are returned as a single comma separated string.
• Numbers are rendered as text. Scores and coordinates come back as plain strings, for example 80 or -75.165220 , which is exactly what Nginx variables expect.
• Empty when not found. If no loaded database contains a field for the client IP, the variable resolves to an empty value. Reference any variable safely, even for databases you did not load.
• Not cached per request. These variables are evaluated each time they are used, so they always reflect the current request's client IP.

Client IP selection and X-Forwarded-For

The module geolocates a single IP address per request. Which one it uses depends on ipgeolocation_trust_forwarded_header .

• Default ( on ): if an X-Forwarded-For header is present, the module reads the first (leftmost) address in it, trimming surrounding spaces. If the header is absent, empty, or unusable, it falls back to the real connection peer address.
• off : the module always uses the real connection peer address and ignores X-Forwarded-For entirely.

A safe setup behind a load balancer:

http {
    ipgeolocation_trust_forwarded_header off;

    set_real_ip_from 10.0.0.0/8;          # your load balancer range
    real_ip_header   X-Forwarded-For;
    real_ip_recursive on;
}

Getting the databases

This module reads IPGeolocation.io MMDB files. You download the databases from your IPGeolocation.io account and point the module at the files. The static download links you receive do not change, so the same paths work for your first download and for every update.

Relevant databases and their documentation:

• IP Geolocation Database: country, state, city, postal code, coordinates, currency, and time zone. Available in Geo Standard and Geo Advance tiers (Advance adds accuracy radius and confidence).
• IP Security Database: threat score plus VPN, proxy, Tor, relay, bot, spam, attacker, corporate gateway, and cloud provider flags. See the IP Security database fields and schema.
• Residential Proxy Database: residential proxy provider name and last seen date.
• IP Hosting Database: hosting provider name.
• IP Company Database: company or ISP name, domain, and type. See the IP Company database schema reference.
• IP to ASN Database: AS number, organization, type, RIR, and allocation date. See the IP to ASN extended database schema.
• IP Abuse Contact Database: abuse email, phone, organization, route, and country. See the IP Abuse Contact database field reference.

You can buy a single database, a ready made bundle (for example IP to Location plus Company plus ASN plus Abuse), or a custom build. Compare IP database pricing and bundles.

After downloading, confirm which fields a file contains with mmdbio:

mmdbio read --db /etc/nginx/ipgeo/db-ip-security.mmdb --ip 2.56.188.34

Updating the databases

IPGeolocation.io publishes refreshed databases daily. Replace the files on disk, then reload Nginx so workers open the new versions.

#!/bin/sh
set -e
DIR=/etc/nginx/ipgeo
URL="https://your-static-download-link"   # from your IPGeolocation.io account

curl -fsSL "$URL" -o "$DIR/db-ip-security.mmdb.tmp"
mv "$DIR/db-ip-security.mmdb.tmp" "$DIR/db-ip-security.mmdb"
nginx -t && nginx -s reload

Schedule it with cron or a systemd timer, for example daily at 04:00: 0 4 * * * /usr/local/bin/update-ipgeo.sh .

Troubleshooting

Nginx fails to start with "failed to open" for a database.

Check that the path in ipgeolocation_db is correct, the file exists, and the Nginx worker user can read it. The module logs the exact error to help you diagnose it.

A variable is always empty.

Confirm you loaded a database that actually contains that field. Security variables need a Security database, ASN variables need an ASN database, and so on (see which databases provide each variable). Use mmdbio read to inspect the file. Also confirm the client IP is what you expect (see how the client IP is selected).

Variables are empty for local or private IPs.

Private and reserved IP ranges (for example 10.0.0.0/8 or 192.168.0.0/16 ) are not in any public geolocation database, so they resolve to empty. This is expected for internal or test traffic. To test real lookups locally, follow Testing your configuration.

Visitors behind a proxy all look like one IP.

Nginx is seeing the proxy's address. Use the realip setup for load balancers with ipgeolocation_trust_forwarded_header off , or keep it on only if your proxy overwrites X-Forwarded-For .

Nginx reports the module "is not binary compatible".

The dynamic module was built against a different Nginx version or without --with-compat . Rebuild it from the exact source version shown by nginx -v (see building as a dynamic module).

The build cannot find maxminddb.h or -lmaxminddb .

Install the libmaxminddb development package (see Requirements). The config file in Installation links the library automatically; for non-standard install paths, pass --with-cc-opt and --with-ld-opt as shown in the static build step.

Frequently Asked Questions

License

See the LICENSE file for details.

Built for IPGeolocation.io databases. Questions about the data, tiers, or bundles are answered in the IPGeolocation.io database documentation and on the IP database pricing page.