FullHunt vs VulDB

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms334360
P95 · ms11561138
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

FullHunt vs VulDB: common questions

Which is more reliable, FullHunt or VulDB?

Both are neck-and-neck — FullHunt and VulDB 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, FullHunt or VulDB?

FullHunt has the lower median latency in our checks — FullHunt responds in 334 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 FullHunt and VulDB need an API key?

Both ask you to authenticate — FullHunt uses an API key and VulDB uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call FullHunt and VulDB from the browser?

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

Are FullHunt and VulDB free for commercial use?

FullHunt 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.