Talk to us
A small team reads every message. We typically reply within one business day.
sales@geoiphub.comSend us a message
Sales and volume pricing, integration help, API questions, billing, or data corrections. If we got an IP wrong, tell us; corrections feed back into the pipeline.
Book a call
Talk to us directly. Useful for Enterprise scoping, procurement questions, or a walkthrough of the API.
Schedule a callJust want to start?
Skip the wait. Grab a free API key with 1,500 lookups a day, every field included, no credit card.
Get a free API keyReport a wrong result
IP data goes stale as ranges change hands, so we want to hear when a location, a VPN flag, or a score looks wrong. Look the IP up in the IP lookup tool first, then send us:
- The IP address, IPv4 or IPv6.
- The field you think is wrong, for example geo.city, detection.is_vpn, or scoring.fraud_score.
- What you expected instead, and why: "this is our office egress", "this is our corporate VPN", "this range moved to a new ISP".
- Any evidence you can share, such as a WHOIS record, your own network documentation, or where the traffic actually originates.
Every verdict is built from the sources on our methodology page, so the more you can tell us about the network, the faster we can trace which source needs fixing.
Getting API help faster
For an integration or API problem, include these so we can skip the back-and-forth:
- The
meta.request_idfrom the response, so we can find the exact lookup. - The IP you looked up and the endpoint you called (GET /v1/lookup/{ip}).
- The HTTP status and message you got back, for example 401 "Invalid API key" or 429 when you hit a rate limit.
- A minimal code sample, with your API key removed.
Status codes, rate limits, and the full response reference are in the API documentation.
Many questions are already answered in the docs, and the free tools let you test any IP without an account.