GeoIP API

GeoIP API is MaxMind's End-of-Life, archived C client library for querying local GeoIP Legacy database files to map IP addresses to geographic and network…

  • Development
  • Network Services
  • Tools & Utilities
GeoIP API is MaxMind's End-of-Life, archived C client library for querying local GeoIP Legacy database files to map IP addresses to geographic and network information, intended for maintaining older codebases rather than new deployments that should use GeoIP2 and libmaxminddb.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

39/100 Low

Maintained
0GitHub repository is archived
Popular
52375 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
95512 MB minimum RAM, runs on ARM
Security check
73no serious findings, CI, tests, OpenSSF Scorecard 4/10
GitHub stars
375
Open issues
0
Last commit
2021-11-24
Latest release
v1.6.12
Activity
stale

Checked 3 days ago - source: GitHub (maxmind/geoip-api-c)

Resources & Compatibility

Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add MaxMind account ID and license key Before the app can fetch IP data, put your MaxMind account ID (your MaxMind account number) and license key in the download or lookup settings. Without these credentials, MaxMind rejects the request and the app has no GeoIP results to return. source
  • Replace license_key in old service calls If you use the old MaxMind web service examples, replace license_key (the sample key in the code) with your real MaxMind license key. A missing or wrong key makes lookup requests fail, so the API can't return city, ISP, or org data. source
  • GeoIP Legacy support MaxMind ended GeoIP Legacy support in May 2022; use GeoIP2 databases and libmaxminddb for current deployments. source
  • End of Life GeoIP Legacy databases were retired in May 2022; the linked C library is end of life, and GeoIP2 with libmaxminddb is recommended. source
  • End of Life / GeoIP2 Migration MaxMind retired GeoIP Legacy databases in May 2022 and the geoip-api-c repo is archived. For new deployments, upgrade to GeoIP2 databases via libmaxminddb. source
  • Legacy end-of-life warning MaxMind retired GeoIP Legacy databases in May 2022; prefer GeoIP2/libmaxminddb for new deployments. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What MaxMind credentials are required before the app can fetch IP data?

You must add your MaxMind account ID and license key to the download or lookup settings. Without these credentials, MaxMind rejects the request and the app has no GeoIP results to return.

Can GeoIP results be used to identify a particular address or household?

No. GeoIP location data is inherently imprecise and often places locations near the center of a population, so it should not be used to identify a particular address or household.

How is the GeoIP Legacy C library built from source on Unix/Linux?

Run ./configure, make, make check, and make install. If you are using a GitHub checkout, run the bootstrap script first to set up the build environment.

Which caching option is useful for larger GeoIP Legacy databases?

GEOIP_INDEX_CACHE caches only the most frequently accessed index portion of the database. It gives faster lookups than GEOIP_STANDARD while using less memory than GEOIP_MEMORY_CACHE.

Answers sourced from dev.maxmind.com, github.com

Community

Collected 49 days ago - public community threads