Admin Dashboard — Test One Mail

Overview

Generated Addresses 0

Processed Emails 0

Awaiting Delivery 0

Authentication Results

SPF Results

DKIM Results

DMARC Results

Diagnostic History

Email Diagnostic History

Date	Test Address	Status	Emails	From	Sender IP	SPF	DKIM	DMARC	Action
Loading...

Guardian & DNSBL Overview

Active Blocklisted IPs 0

24h DNS Blocklist Queries 0

24h Ban Ingestions 0

Monitored Guardian IPs 0

Real-Time Usage & Traffic (Last 24 Hours)

DNS Usage Graph (Blocklist Checks)

Queries to bl.testonemail.com: Hits (Blocked Attackers) vs Clean Lookups

Active

API Usage Graph (Bans & Reputation)

Fail2ban ban reports received vs public reputation checks

Live

Active Blocklist Directory (bl.testonemail.com)

Active Blocklisted IPs

IPs currently returning positive DNSBL blocks. Search, inspect levels, or manually delist.

Offending IP	Level	Return Code	Threat Category	Strikes	Last Seen	Expires In	Action
Loading active listings...

Recent Threat Intel Ingestion Logs

Live Ban Reports Received From Your Servers

Attacking IPs reported by your Fail2ban jails (Dovecot, Postfix) and DMARC sync.

Reported At	Offending IP	Server Source	Jail	Target & Incident Log Excerpt
Loading reports...

RBL Threat Intel Ingestion Keys

Authorized Mail Servers (Fail2ban Exporters)

Only mail servers with authorized API keys can report attacker IPs into TestOneMail RBL.

Server Identifier	API Key	Created	Last Used	Action
Loading keys...

Fail2ban Integration Guide (Admin Only)

Deploying to Your Mail Servers

Configure your mail servers (Dovecot, Postfix, Nginx) to report banned IPs directly to TestOneMail RBL alongside AbuseIPDB.

1. Download Action File

sudo curl -sSL https://blocklist.testonemail.com/testonemail.conf -o /etc/fail2ban/action.d/testonemail.conf

2. Recommended: Direct Action (No Macro Interpolation Errors)

Edit /etc/fail2ban/action.d/testonemail.conf and set your API key in [Init]:

[Init]
testonemail_apikey = YOUR_SERVER_API_KEY

Then in any jail in /etc/fail2ban/jail.local (e.g. [dovecot], [postfix]), simply append testonemail:

[dovecot]
action = nftables-multiport[name=dovecot, port="80,443,25,587,465,110,995,143,993,4190", protocol=tcp]
         banned_db[name=dovecot, port="80,443,25,587,465,110,995,143,993,4190", protocol=tcp]
         %(action_abuseipdb)s[abuseipdb_category="18"]
         testonemail

[postfix]
action = nftables-multiport[name=postfix, port="80,443,25,587,465,110,995,143,993,4190", protocol=tcp]
         banned_db[name=postfix, port="80,443,25,587,465,110,995,143,993,4190", protocol=tcp]
         %(action_abuseipdb)s[abuseipdb_category="18,11"]
         testonemail

Alternative: Macro Style with %(action_testonemail)s

If using %(action_testonemail)s, both testonemail_apikey and action_testonemail must be declared at the top of /etc/fail2ban/jail.local under [DEFAULT] so all jails can interpolate it:

[DEFAULT]
testonemail_apikey = YOUR_SERVER_API_KEY
action_testonemail = testonemail[testonemail_apikey="%(testonemail_apikey)s"]

Admin Sign In