dead-drop vs FilterLists
Same instrument, two spec sheets — measured, not claimed.
dead-drop vs FilterLists: common questions
Which is more reliable, dead-drop or FilterLists?
On our scheduled checks, dead-drop leads on measured uptime — dead-drop at 99.02% versus FilterLists at 98.0% 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, dead-drop or FilterLists?
FilterLists has the lower median latency in our checks — dead-drop responds in 722 ms versus FilterLists at 357 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 dead-drop and FilterLists need an API key?
Neither needs a paid key — dead-drop 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 dead-drop and FilterLists from the browser?
Only dead-drop 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 dead-drop and FilterLists free for commercial use?
dead-drop 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.