dead-drop vs Portscan
Same instrument, two spec sheets — measured, not claimed.
dead-drop vs Portscan: common questions
Which is more reliable, dead-drop or Portscan?
On our scheduled checks, Portscan leads on measured uptime — dead-drop at 99.44% versus Portscan at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, dead-drop or Portscan?
Portscan has the lower median latency in our checks — dead-drop responds in 458 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 dead-drop and Portscan need an API key?
Neither needs a paid key — dead-drop 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 dead-drop and Portscan from the browser?
Yes — both dead-drop and Portscan send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.
Are dead-drop and Portscan free for commercial use?
dead-drop 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.