shipapis
StarSubmit an APISubmit API

GeoJS vs IPWhois

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

APIGeoJSHEALTHY100IPWhoisHEALTHY100
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms10723
P95 · ms722598
AuthnoneapiKey
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API key requiredFree tier — API key may be required for production
Rate limitUnpublished (no enforced limit stated)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoJS vs IPWhois: common questions

Which is more reliable, GeoJS or IPWhois?

Both are neck-and-neck — GeoJS 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, GeoJS or IPWhois?

IPWhois has the lower median latency in our checks — GeoJS responds in 107 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 GeoJS and IPWhois need an API key?

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

Can I call GeoJS and IPWhois from the browser?

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

GeoJS 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.