A GeoIP service that can be a REST API or command line tool.
The only dependencies that this app has are Gin, for setting up a webserver, and govalidator, for validating input.
go build .Usage of ./geoip-service:
-dns-servers string
The list of DNS servers. If not specified defaults to Cloudflare, Google, and OpenDNS
-domain string
A domain name
-ext-dir string
Specify the location of the folder containing the extensions
-ip string
An IP address
-pub-dir string
Specify the location of the public folder (to serve a front end)
-serve
Run the HTTP server
-sip string
The IP to serve on (127.0.0.1 will make it accessible only from localhost) (default "127.0.0.1")
-whitelist string
If specified, it will only allow (only used with -serve)
# To query right from the command line.
./geoip-service -domain one.one.one.one
./geoip-service -ip 1.1.1.1
# To run the HTTP API.
./geoip-service -serve
# To serve on a specific iface.
./geoip-service -serve -sip 0.0.0.0
# You can also add a whitelist of IPs to allow to access the API and a custom list of
# DNS servers to query.
./geoip-service -serve -whitelist ./whitelist -sip 0.0.0.0 -dns-servers ./dns_serversThe -pub-dir flag can be used to specify a front end application that calls all the APIs. There's an example of this in the geoip-service-fe repository.
The app has an integrated extension engine which is mostly meant to be used when running it as an API server. An extension can register API endpoints, run cron jobs, and manage data on their own, which the main app can query. Below you'll find an example of an extension that queries data from a 3rd party IP list.
See the full documentation on extensions here.
Although the source code is licensed under GNU GPLv3, I prohibit the use of this code for the purpsoses of training any kind of AI model. This applies to any version of the source code and/or commit, historic, current, and/or new.