Launching soon? Check where your launch email lands before you send it
Hey makers π
On launch day, most of us email our users, our list, our network. Almost nobody checks where that email actually lands.
If it goes to spam, the launch loses its warmest traffic source. And nobody tells you.
So we built a free tool for it: the Mailwarm Email Deliverability Test.
How it works
Start the test and get a unique test address
Send your real email to it, from the tool and domain you normally use
About a minute later, your report is ready
What the report shows
A score out of 100. The same email always gets the same score, so you can re-test after each fix and see exactly what changed
Placement estimates for Gmail, Outlook, Yahoo and Apple Mail
SPF, DKIM and DMARC results, including alignment with your From domain
Your sending IP and domain checked against major blacklists
Your DNS setup: MX, PTR, MTA-STS, TLS-RPT, BIMI
A SpamAssassin score with every rule that fired
Every fix, ranked by priority
One honest caveat: a great score isn't a reputation. A brand-new domain can score 95 and still land in spam until it has built trust. We say it upfront, because a score that flatters you is useless.
π Run the free test
If you're launching in the next few weeks: run it on your actual launch email and drop your score below. I'll help you read the report and fix what's flagged before your big day.
And if you've already tested: what was the first issue it found?
Thami


Replies
It seems I need some serious fixing!
Very useful tool, @thamibenjelloun . Thank you!
Whatβs the technology behind the test?
Thanks @ilyasbΒ for sharing your score π
The good news is that 37 is mostly an authentication problem, and you can fix that in under an hour:
Add an SPF record for elywo.com: v=spf1 include:_spf.google.com ~all
Turn on DKIM for your own domain in Google Admin (Apps > Google Workspace > Gmail > Authenticate email). Right now Google signs with its default domain, so DKIM doesn't align with elywo.com.
Then add a DMARC record, starting with p=none so you can monitor safely.
Run the test again after that.
How it works: you send a real email to the test address, and we read what actually arrives. That covers SPF, DKIM and DMARC with alignment, blacklists for your IP and domain, DNS (MX, PTR, MTA-STS, BIMI), and SpamAssassin rules.
All of that goes into the score and a list of fixes in order. @karimbenkeroum built it and can tell you more about the technical side πͺπ»
If you'd like a hand with the setup, you can jump on a quick call with one of our email Deliverability experts and walk through it live.
You can book a call on Mailwarm.com ππ»
For me, checking SPF, DKIM, and DMARC before a launch should be part of the preparation checklist. Fixing these issues early is much better than dscovering them afterward.
The ability to retest the same email after each fix sounds practical. Iβd find it helpful to see exactly which changes improved the results