test your email’s
deliverability score in 30 seconds.
send a real campaign email to a one-shot test address. we run it through the same SPF / DKIM / DMARC / RBL / content checks that gmail and outlook use, and give you a 10/10 score with a per-category breakdown. no signup. results expire in 24 hours.
how it works
- step 1
click start
we generate a one-shot address like
test-AB12CD34@check.adbtd.com. - step 2
send your email
from your real sending stack — same headers, same IP, same DKIM. we receive it on port 25, parse, and score.
- step 3
read your score
10/10 = perfect. each category (auth, identity, reputation, content, transport) breaks down what’s wrong and what to fix.
this tool is free because we already run the infrastructure.
adbtd runs full email infrastructure on bare metal — your own SMTP, IMAP, and a virgin dedicated IP under your domain. recipients see you. we don’t appear in the headers, the DNS, or the conversation.
the deliverability checks here are the same ones we run continuously on customer traffic. we wrote this tool so you can audit your current setup before signing up — or audit ours, if you’re already a customer.
learn more about adbtd →frequently asked
- what does the score mean?
- 0–10, higher is better. mail-tester convention. we map rspamd's spam score (where higher = spammier) into a 10-point readability score. 10/10 means rspamd had nothing to flag at all.
- do you store my email?
- the raw message lives in redis with a 24-hour TTL, then it's gone. no backups. the result page at the same URL also expires after 24 hours.
- can you read the email body?
- we never render the email body in the result page — only headers and computed metadata. the raw text exists in redis just long enough to score it.
- why the 10/day per-IP cap?
- abuse prevention. inbox-warming bots and scrapers will hammer this otherwise. legitimate testing rarely needs more than that. existing adbtd customers get unlimited via API.
- what happens if my email never arrives?
- the result page polls for 5 minutes. if nothing shows up, your sending stack rejected the message before it left, or your test address was blocked at our edge (size > 5MB, malformed envelope, etc.). check your sending logs.