mint

lookup · network

IP address lookup online

Enter a public IPv4 or IPv6 address and get its reverse DNS name and registry record — network block, name, and country — in JSON; each call uses 1 credit after the 20 free runs a day.

input

Public IPv4 or IPv6 address

ctrl + enter

result

Press Run. The result lands here, made by the real tool.

1 credit · ≤25 s · no login · 20 free/day

How it works

  1. Type or paste a public IPv4 or IPv6 address into the address field.
  2. Press Run; the lookup completes within 25 seconds.
  3. Read the JSON result — IP version, reverse DNS records, and registry network details.

Limits

You can run the lookup twenty times a day without logging in. Each run beyond that costs 1 credit drawn from a prepaid balance attached to your API key. Input is capped at 4.096 KB.

Privacy

Your input address is processed for the request and discarded afterwards; it is not kept or used for anything else. Usage records store only time, tool, status, duration, credits, and a salted hash of the IP.

Call it from code

curl
curl -sS -X POST 'https://data.voiddo.com/v1/ip_lookup' \
  -H 'Content-Type: application/json' \
  -d '{"ip":"1.1.1.1"}'

20 calls a day need no key. Beyond that: one-time credit packs, $5 for 500 credits, $9 for 1,000 credits, $29 for 4,000 credits. Get credits · llms.txt · OpenAPI.

Questions

What data does the result include?

The JSON contains the IP address, its version, whether it is private, all reverse DNS names, and registry fields for the network block such as name and country.

Does this work for both IPv4 and IPv6?

Yes, you can enter any public IPv4 or IPv6 address.

How do I call this from code?

Send a POST request to https://data.voiddo.com/v1/ip_lookup with your address; a curl example is shown on this page.

What happens once I have used the twenty free runs?

Further calls require an API key with a prepaid credit balance; each call costs 1 credit.

Is my input address stored?

No, the address is discarded after the request completes; only a salted hash is kept in the usage record alongside timing and status fields.