shipapis
StarSubmit an APISubmit API

Authentication vs Portscan

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

APIAuthenticationNEW—PortscanNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Authentication vs Portscan: common questions

Which is more reliable, Authentication or Portscan?

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

Neither needs a paid key — Authentication is callable with no signup, and Portscan is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Authentication and Portscan from the browser?

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

Are Authentication and Portscan free for commercial use?

Authentication has unclear commercial terms, and Portscan 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.