ip.app vs IPWhois

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms7623
P95 · ms276598
AuthnoneapiKey
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ip.app vs IPWhois: common questions

Which is more reliable, ip.app or IPWhois?

Both are neck-and-neck — ip.app and IPWhois each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, ip.app or IPWhois?

IPWhois has the lower median latency in our checks — ip.app responds in 76 ms versus IPWhois at 23 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do ip.app and IPWhois need an API key?

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

Can I call ip.app and IPWhois from the browser?

Only ip.app 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 ip.app and IPWhois free for commercial use?

ip.app has unclear commercial terms, and IPWhois 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.