EmailRep vs Portscan
Same instrument, two spec sheets — measured, not claimed.
EmailRep vs Portscan: common questions
Which is more reliable, EmailRep or Portscan?
On our scheduled checks, EmailRep leads on measured uptime — EmailRep at 100% versus Portscan at 99.02% 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, EmailRep or Portscan?
EmailRep has the lower median latency in our checks — EmailRep responds in 277 ms versus Portscan at 335 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 EmailRep and Portscan need an API key?
Neither needs a paid key — EmailRep 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 EmailRep and Portscan from the browser?
Only Portscan is browser-friendly — it returns CORS headers over HTTPS. EmailRep needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are EmailRep and Portscan free for commercial use?
EmailRep 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.