shipapis
StarSubmit an APISubmit API

IPWhois vs SLF

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

APIIPWhoisHEALTHY100SLFHEALTHY98
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms23213
P95 · ms598668
AuthapiKeynone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — static file, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPWhois vs SLF: common questions

Which is more reliable, IPWhois or SLF?

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

IPWhois has the lower median latency in our checks — IPWhois responds in 23 ms versus SLF at 213 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 IPWhois and SLF need an API key?

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

Can I call IPWhois and SLF from the browser?

Only SLF 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 SLF free for commercial use?

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