Security · head-to-head

dead-drop vs FilterLists

dead-drop

dead-drop is a minimal, self-hostable API for sharing ephemeral secrets: the client encrypts the payload before it ever reaches the server, so the backend only ever stores ciphertext it cannot read, and each secret can be set to self-destruct after a single view or a time limit. It needs no account or API key — requests are simply rate-limited per IP — and returns plain JSON over a small REST surface. The design mirrors the classic one-time-secret pattern used for sharing passwords or tokens without leaving a permanent copy anywhere.

FilterLists

FilterLists is Collin Barrett's independent, actively-maintained directory of filter and host lists used by adblockers, firewalls, and DNS sinkholes to block ads, trackers, malware, and other unwanted content. Its ASP.NET Core REST API serves the same catalog that powers the site -- filter lists, the domains/URLs they target, licenses, and maintainer info -- with an interactive Swagger UI for exploring the schema before writing a query. The API and site are fully free and keyless, open-sourced on GitHub with commits as recent as this week. The API lives entirely on a separate `api.filterlists.com` host -- the intuitive REST paths on the main `filterlists.com` domain just return the site's own SPA shell.

dead-dropFilterLists
AuthenticationNoneNone
Pricingfreefree
FormatsJSONJSON
CORSyesno
HTTPSYesYes

dead-drop supports CORS, while FilterLists doesn't — pick dead-drop for direct browser calls.

More comparisons