Hysen LabsReal-time phishing & scam domain blocklist, 190k+ curated threats, 888K+ community, free API, multiple formats.
Real-time phishing & scam domain blocklist, 190k+ curated threats, 888K+ community, free API, multiple formats.
The project context on this page is free to read. The original GitHub repository remains the source of truth; sign in only when you want to save or join the discussion.
Teams evaluating Security & Privacy and Developer Tools
Developers working with Other language, Security & privacy, and Web service
Readers comparing actively maintained open-source alternatives
This practical context is free to read. Use it as a starting point for evaluating destroylist; the repository, issue tracker and license remain the source of truth.
Start with the HTML implementation and the Security & Privacy and Developer Tools classification, then follow the repository structure and documented interfaces before adopting it.
Compare the project against its Other language, Security & privacy, and Web service use cases, paying attention to maintenance activity, operational complexity and the license terms.
Pin a release, review open issues, test failure and upgrade paths, and add monitoring and access controls before putting it on a critical path.
We've laid out the answer right above — check the Best Fit section for primary use cases, then scan the tags and categories in the sidebar. Between those three signals, you'll have a solid picture of where destroylist shines (and where it doesn't).
The repo is under MIT. That said, licenses occasionally change between versions, so always double-check the LICENSE file in the repository before you commit to anything.
The GitHub stats you see here refresh daily through an automated snapshot job. The editorial notes get updated when something meaningful happens — a major release, a license change, or a noticeable shift in the community around destroylist.
Please do! Scroll down to the Community Notes section and drop a comment with the repo link. We pay close attention to what the community is watching — and strong suggestions often graduate into full editorial reviews.
We unpack architecture signals, production trade-offs, and a pre-flight checklist for teams evaluating destroylist. Use it as practical context alongside the repository, issue tracker and license.
Community notes