2.8 KiB
2.8 KiB
Report a Phishing Domain
| Method | Link | Speed |
|---|---|---|
| Telegram bot | @PhishDestroy_bot | Instant |
| API | api.destroy.tools | Instant |
| GitHub issue | Blocklist addition → | Reviewed |
Include evidence where possible: screenshots, VirusTotal or URLScan links.
Request Domain Removal (False Positive)
| Method | Link |
|---|---|
| Appeals form | phishdestroy.io/appeals |
| GitHub issue | Appeal → |
Approved domains are added to allow/allowlist.json and automatically cleaned from all lists.
Code or Pipeline Contributions
# Fork & clone
git clone https://github.com/YOUR_USERNAME/destroylist.git
cd destroylist
# Create a branch
git checkout -b feature/my-improvement
# Install dependencies
pip install -r requirements.txt
# Validate before submitting
python scripts/validate_json.py
python scripts/validate_and_clean.py
python scripts/build_rootlist.py
# Open a Pull Request with a clear description
Add a New Community Source
If you maintain a publicly accessible, regularly updated phishing feed and want it aggregated into the Community list:
- Open an issue with the feed URL and format (JSON array, plain text, hosts file, etc.)
- We'll review and add it to
scripts/smart_aggregator.py
Current sources: MetaMask, ScamSniffer, OpenPhish, SEAL, Phishunt, Enkrypt, CryptoFirewall, DiscordPhishing, Polkadot, SPMedia, Codeesura and more.
Guidelines
| Rule | Reason |
|---|---|
| JSON files must be valid and sorted | Consistency, clean diffs |
| No IP addresses in domain lists | We block domains, not IPs |
| No duplicates | Clean data |
| Respect the allowlist | Never re-add an allowed domain |
| One fix or feature per PR | Easier review |
