shipapis
StarSubmit an APISubmit API

IPWhois vs PostalCodes

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

APIIPWhoisNEW—PostalCodesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPWhois vs PostalCodes: common questions

Which is more reliable, IPWhois or PostalCodes?

On our scheduled checks, PostalCodes leads on measured uptime — IPWhois at —% versus PostalCodes 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 PostalCodes need an API key?

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

Can I call IPWhois and PostalCodes from the browser?

Neither sends browser-friendly CORS headers reliably, so call IPWhois and PostalCodes from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are IPWhois and PostalCodes free for commercial use?

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