Whitelist inputs

The reviewed general whitelist uses Tranco, maintained anudeepND allowlists and operator-maintained additions. These inputs help reduce false positives; they are separate from the phishing intelligence providers above.

How source data is used

Phishing Army consumes live or bounded current snapshots. It does not crawl these providers as a historical archive and does not carry an indicator forward merely because it appeared in an older build.

What Phishing Army adds

The project adds careful source selection, resilient collection, domain normalization, conservative parent-domain handling, whitelist policy, shared-platform protection, deduplication, multiple output formats and reliable high-volume distribution.

Source changes

Feeds may be added or removed when their relevance, freshness, false-positive rate or redistribution terms change. The corresponding implementation details and decisions are maintained in the Core source registry.