CVEDB vs FilterLists
Same instrument, two spec sheets — measured, not claimed.
CVEDB vs FilterLists: common questions
Which is more reliable, CVEDB or FilterLists?
On our scheduled checks, CVEDB leads on measured uptime — CVEDB at 99.44% versus FilterLists at 97.2% 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, CVEDB or FilterLists?
CVEDB has the lower median latency in our checks — CVEDB responds in 196 ms versus FilterLists at 303 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 CVEDB and FilterLists need an API key?
Neither needs a paid key — CVEDB 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 CVEDB and FilterLists from the browser?
Neither sends browser-friendly CORS headers reliably, so call CVEDB and FilterLists from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.
Are CVEDB and FilterLists free for commercial use?
CVEDB 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.