# 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 information, intended for maintaining older codebases rather. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5861/geoip-api

## Description

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.

## Health score

39/100 (Low), based on 5 of 5 factors.
- Maintained: 0 (GitHub repository is archived)
- Popular: 52 (375 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 95 (512 MB minimum RAM, runs on ARM)
- Security check: 73 (no serious findings, CI, tests, OpenSSF Scorecard 4/10)

## Links

- GitHub: https://github.com/maxmind/geoip-api-c
- Docker Hub: https://hub.docker.com/r/observabilitystack/geoip-api

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/5861/geoip-api), the self-hosted and open-source app directory.
