Pius Plugins - All 23 Discovery Plugins

Pius includes 23 discovery plugins: 14 for domain discovery and 9 for CIDR (IP range) discovery. Plugins are organized into passive (OSINT-only, default) and active (sends network probes, opt-in) modes.

How do Pius plugins work?

Each plugin implements a standard interface and self-registers at startup. Plugins that require API keys check for them before running -- if the key is missing, the plugin is silently skipped. No configuration changes are needed; just set the environment variable and the plugin activates.

Plugin summary

Category	Count	Mode	Examples
Domain (passive)	8	Default	crt-sh, passive-dns, reverse-whois, gleif, wikidata
Domain (active)	6	Opt-in	dns-brute, dns-zone-transfer, doh-enum, favicon-hash
CIDR (passive)	9	Default	whois, arin, ripe, apnic, afrinic, lacnic, asn-bgp

List available plugins

pius list

Detailed plugin documentation

• Domain Plugins - Certificate transparency, passive DNS, WHOIS, GitHub, GLEIF, Wikidata, DNS brute-force, zone transfer, DoH enumeration, favicon hashing, and more
• CIDR Plugins - All 5 RIRs (ARIN, RIPE, APNIC, AFRINIC, LACNIC), BGP tables, Shodan, WHOIS handle discovery, SEC EDGAR

Which plugins require API keys?

Plugin	Environment Variable	Required?
apollo	APOLLO_API_KEY	Yes
passive-dns	SECURITYTRAILS_API_KEY	Yes
reverse-whois	VIEWDNS_API_KEY	Yes
favicon-hash	SHODAN_API_KEY	Yes
favicon-hash	FOFA_API_KEY	No (optional)
github-org	GITHUB_TOKEN	No (raises rate limit)
reverse-ip	VIEWDNS_API_KEY	No (optional)
doh-enum	AWS credentials	No (only for --doh-deploy-gateways)

Can I run Pius without any API keys?

Yes. These plugins require no authentication:

• crt-sh (needs --domain)
• gleif, whois, edgar, wikidata, google-dorks
• arin, ripe, apnic, afrinic, lacnic
• asn-bgp (needs --asn)
• github-org (optional token for higher rate limits)
• dns-brute, dns-zone-transfer, doh-enum (active mode, no auth needed)