Getting started
Operator-grade phishing and abuse reputation with community input. Six steps, from account creation to a domain-first blocking workflow — but pick the path that matches your job rather than doing all six.
Protect your mail server with DNSBL, agent, or API lookups.
Submit reports, vote on threats, track phishing kits.
Integrate threat feeds into your app or SIEM.
Create an account
Register at /account/login. Enter your email address, a public display name, and a password. A verification email will be sent automatically — click the link inside to activate your account.
Email verification is required before you can submit reports or cast votes. Accounts without a verified email are read-only.
Submit your first report
Go to /submit and choose an IOC type:
Include evidence in the description — e.g. email headers, a brief explanation of the threat, or a reference to a related campaign. Reports with clear evidence are easier to enrich, score, and review accurately. URL submissions are normalized into canonical domains for long-term phishing intelligence. For shared platforms, submit the tenant host or full URL rather than the platform parent.
Get your API key
Go to /account and open the API Keys tab. Create a key with read scope for lookups or write scope to submit reports programmatically. The raw key is shown exactly once — save it securely.
# Query reports via API
curl -s "https://api.vspam.org/api/v1/public/reports?q=paypal" \
-H "Authorization: Bearer YOUR_API_KEY"
# Operator lookup for a phishing domain
curl -s "https://api.vspam.org/api/v1/public/operator-lookup?type=domain&value=login-paypa1.com"
# Operator lookup for ASN context
curl -s "https://api.vspam.org/api/v1/public/operator-lookup?type=asn&value=AS13335"
# Check exact IP or IPv6 host reputation
curl -s "https://api.vspam.org/api/v1/rbl/check?ip=185.234.72.19"Integrate with your infrastructure
5 routesChoose the integration method that fits your setup:
See integration guides for Postfix, rspamd, SpamAssassin, and Fail2Ban, or firewall feeds for network-level blocking, or API docs for the full endpoint reference. For product-specific guidance, start with domain reputation, IPv6 intelligence, and ASN reputation.
Deploy the mail agent
The vspam-agent is a lightweight Go sidecar that checks IOCs during SMTP policy evaluation with local BoltDB caching. The agent fails open on its own errors — but Postfix does not by default, which is what the two smtpd_policy_service_* lines below are for.
# Debian/Ubuntu (via repo)
sudo apt update && sudo apt install vspam-agent
# Configure
sudo vim /etc/vspam/agent.yml # set api_key
# Start & add to Postfix
sudo systemctl enable --now vspam-agent
# Add to /etc/postfix/main.cf:
# smtpd_policy_service_default_action = DUNNO
# smtpd_policy_service_timeout = 10s
# check_policy_service inet:127.0.0.1:10045Packages for Debian/Ubuntu, RHEL/CentOS, and manual tarballs at /download.
Vote & build your reputation
Every account has a trust tier that affects how much weight your votes carry. Build reputation by submitting accurate reports and voting on others:
Browse pending reports to vote on, or check the leaderboard to see top contributors.
Prerequisites
Troubleshooting
Check spam/junk. Emails are sent from noreply@vspam.org.
Pass the key in Authorization: Bearer or the X-API-Key header.
Try dig +short test.dnsbl.vspam.org. Ensure your resolver doesn't strip RPZ records.
Check journalctl -u vspam-agent. Common causes: missing config, port conflict.
Free tier = 500 req/hour. Build trust tier for higher limits, or contact support@vspam.org.