Icanhazip vs staffSign

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

Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Icanhazip vs staffSign: common questions

Which is more reliable, Icanhazip or staffSign?

Both are neck-and-neck — Icanhazip and staffSign each measure 0.0% 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.

Do Icanhazip and staffSign need an API key?

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

Can I call Icanhazip and staffSign from the browser?

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

Are Icanhazip and staffSign free for commercial use?

Icanhazip has unclear commercial terms, and staffSign 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.