Shodan EntityDB API vs staffSign

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSnono
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

Shodan EntityDB API vs staffSign: common questions

Which is more reliable, Shodan EntityDB API or staffSign?

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

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

Can I call Shodan EntityDB API and staffSign from the browser?

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

Are Shodan EntityDB API and staffSign free for commercial use?

Shodan EntityDB API 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.