Portscan vs VulDB

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms335360
P95 · ms7341138
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Portscan vs VulDB: common questions

Which is more reliable, Portscan or VulDB?

On our scheduled checks, VulDB leads on measured uptime — Portscan at 99.02% versus VulDB 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, Portscan or VulDB?

Portscan has the lower median latency in our checks — Portscan responds in 335 ms versus VulDB at 360 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 Portscan and VulDB need an API key?

Portscan needs no key, while VulDB requires a free API key. If you want to start calling without signup, reach for Portscan first.

Can I call Portscan and VulDB from the browser?

Yes — both Portscan and VulDB 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 Portscan and VulDB free for commercial use?

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