Offline Datasets

Offline Datasets

This page explains how ReconSR uses local offline databases for enrichment modules that do not query a remote API at runtime.

Offline database modules expose their functions only when the required database files are installed locally. You must obtain these databases independently from the relevant providers and place them in the expected local data directories.

If the required files are absent, the related functions are not returned to the dispatcher and are not scheduled for execution.

Supported Offline Database Modules

ReconSR currently uses offline datasets for two modules:

• ip2location
• maxmind

Each module expects its own local directory under data/. ReconSR does not create these dataset directories automatically. Create the directory for each offline module you want to use and place only the database files you need there.

IP2Location Module

The ip2location module uses IP2Location and IP2Proxy database files for IP geolocation, ASN, and proxy-related enrichment.

Official website: https://www.ip2location.com/

Create the directory and place IP2Location database files in:

data/ip2location

IP2Location File Priority

ReconSR checks database files in priority order. Premium database names are checked first. If a premium database is not present, ReconSR checks the Lite alternative.

Dataset Purpose	Priority Order
Geolocation	IP2LOCATION-DB11.IPV6.BIN → IP2LOCATION-LITE-DB11.IPV6.BIN
ASN	IP2LOCATION-ASN.IPV6.BIN → IP2LOCATION-LITE-ASN.IPV6.BIN
Proxy	IP2PROXY-PX12.BIN → IP2PROXY-LITE-PX12.BIN

Example directory layout:

data/ip2location/
├── IP2LOCATION-DB11.IPV6.BIN
├── IP2LOCATION-ASN.IPV6.BIN
└── IP2PROXY-PX12.BIN

Lite database example:

data/ip2location/
├── IP2LOCATION-LITE-DB11.IPV6.BIN
├── IP2LOCATION-LITE-ASN.IPV6.BIN
└── IP2PROXY-LITE-PX12.BIN

MaxMind Module

The maxmind module uses MaxMind database files for IP geolocation, ASN/ISP, enterprise, and anonymous IP enrichment.

Official website: https://www.maxmind.com

Create the directory and place MaxMind database files in:

data/maxmind

MaxMind File Priority

ReconSR checks database files in priority order. Premium database names are checked first. If a premium database is not present, ReconSR checks the available lower-tier alternatives.

Dataset Purpose	Priority Order
Enterprise	GeoIP2-Enterprise.mmdb
City	GeoIP2-City.mmdb → GeoLite2-City.mmdb
ASN / ISP	GeoIP2-ISP.mmdb → GeoIP2-ASN.mmdb → GeoLite2-ASN.mmdb
Proxy / Anonymous IP	GeoIP-Anonymous-Plus.mmdb → GeoIP2-Anonymous-IP.mmdb

Example Enterprise directory layout:

data/maxmind/
├── GeoIP2-Enterprise.mmdb
└── GeoIP-Anonymous-Plus.mmdb

The Enterprise database includes City and ISP-level data, so GeoIP2-City.mmdb and GeoIP2-ISP.mmdb are not needed in this layout.

Example paid non-Enterprise directory layout:

data/maxmind/
├── GeoIP2-City.mmdb
├── GeoIP2-ISP.mmdb
└── GeoIP-Anonymous-Plus.mmdb

Alternative paid non-Enterprise layout:

data/maxmind/
├── GeoIP2-City.mmdb
├── GeoIP2-ASN.mmdb
└── GeoIP2-Anonymous-IP.mmdb

Example Lite directory layout:

data/maxmind/
├── GeoLite2-City.mmdb
└── GeoLite2-ASN.mmdb

File Resolution Behavior

For each dataset category, ReconSR uses the first matching file found in the configured priority order. This allows paid databases and Lite databases to use the same module path while preserving the preferred processing order.

If none of the expected files for a module are present, the module does not expose its functions to the dispatcher.