One dataset, several integrations

Choose the format your software understands.

Every format is generated from the same balanced canonical domain set and published under the stable /download/ path.

Domains

One normalized domain per line. The canonical Phishing Army feed.

For: Pi-hole, AdGuard Home, DNS filters and custom integrations

/download/phishing-army-domains.txt

Download Domains

Adblock

Adblock-style DNS rules using the ||domain^ syntax.

For: uBlock Origin, AdGuard, Pi-hole and compatible blockers

/download/phishing-army-adblock.txt

Download Adblock

Hosts

Hosts-file entries mapped to 0.0.0.0.

For: Hosts-file consumers and network filtering tools

/download/phishing-army-hosts.txt

Download Hosts

DNSMasq

Ready-to-include DNSMasq local rules.

For: DNSMasq 2.86 or newer and compatible integrations

/download/phishing-army-dnsmasq.conf

Download DNSMasq

Wildcard

Asterisk-prefixed wildcard domains.

For: Blocky, Nebulo, OPNsense, YogaDNS and compatible tools

/download/phishing-army-wildcard.txt

Download Wildcard

Unbound

Unbound local-zone entries returning NXDOMAIN.

For: Unbound recursive resolvers

/download/phishing-army-unbound.conf

Download Unbound

RPZ

Response Policy Zone with domain and subdomain coverage.

For: BIND, Knot Resolver, PowerDNS, Unbound and RPZ consumers

/download/phishing-army-rpz.zone

Download RPZ

Hostname and subdomain coverage

Every file uses the same reported hostnames, but the matching behavior depends on the format and the software importing it. Hosts entries match the listed hostname exactly. Adblock, DNSMasq, Unbound and RPZ rules also cover its subdomains. A plain domains feed follows the matching rules of your chosen DNS filter. Wildcard behavior depends on the consumer; Blocky includes both the hostname itself and its subdomains.

These rules do not add a tenant's parent domain. For example, a rule for phishing.netlify.app can also cover names below that tenant without blocking netlify.app or unrelated tenants.

Resolver configuration files

DNSMasq, Unbound and RPZ files must be loaded through the resolver's configuration. Download the chosen file, validate the resulting configuration and reload it using the procedure for your resolver. Configure periodic downloads and reloads if your software does not manage feed updates automatically.

Compatibility endpoints

The historic files phishing_army_blocklist.txt and phishing_army_blocklist_extended.txt remain available for existing integrations. They are byte-for-byte identical to the canonical domains feed.

Machine-readable manifest

The JSON manifest reports the generation time, entry count, source status, file sizes and SHA-256 hashes for the current publication.