Authentication vs Portscan
Same instrument, two spec sheets — measured, not claimed.
Authentication vs Portscan: common questions
Which is more reliable, Authentication or Portscan?
Both are neck-and-neck — Authentication and Portscan 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, Authentication or Portscan?
Authentication has the lower median latency in our checks — Authentication responds in 162 ms versus Portscan at 225 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 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.