IPWhois vs Administrative Divisions DB

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (see repo)
Free tierFree tier — API key may be required for productionFree, no API key required (static JSON via CDN)
Rate limitUnpublishedNone (static files served over CDN)
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPWhois vs Administrative Divisions DB: common questions

Which is more reliable, IPWhois or Administrative Divisions DB?

On our scheduled checks, Administrative Divisions DB leads on measured uptime — IPWhois at —% versus Administrative Divisions DB at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do IPWhois and Administrative Divisions DB need an API key?

Administrative Divisions DB needs no key, while IPWhois requires a free API key. If you want to start calling without signup, reach for Administrative Divisions DB first.

Can I call IPWhois and Administrative Divisions DB from the browser?

Only Administrative Divisions DB is browser-friendly — it returns CORS headers over HTTPS. IPWhois needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are IPWhois and Administrative Divisions DB free for commercial use?

IPWhois has unclear commercial terms, and Administrative Divisions DB has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.