Portscan vs FilterLists

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

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

Portscan vs FilterLists: common questions

Which is more reliable, Portscan or FilterLists?

Only FilterLists is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Portscan and FilterLists need an API key?

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

Can I call Portscan and FilterLists from the browser?

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

Are Portscan and FilterLists free for commercial use?

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