"Testing a message with your inbox"

Every domain can have an intake address. Mail sent to it lands on the domain's Inbox tab, where we read it the way a receiving server would.

What to send

• A test from your own mail system. Send a normal message from the system you use (your mail app, your newsletter tool, your app's sender) to the intake address. This is the best test: we see exactly what a receiver sees.
• A message that went to spam. Forward it as an attachment (in most mail apps: More, then Forward as attachment). We read the attached original, with what its receiver recorded. A normal forward only shows us the forward itself.

What the score means

The score starts at 10 and loses points for things receivers care about: SPF, DKIM and DMARC not passing, a passing check that isn't aligned with the From domain, a blocklist listing, bulk mail without a one-click unsubscribe, and Microsoft's own spam ratings. Every point it loses comes with the reason. A guess (like "this looks like bulk mail") costs half.

A high score doesn't promise the inbox: receivers also weigh your sending history and how people respond to your mail. A low score points at what to fix first.

Keeping it private

We never show a message's body, only facts about it (its parts, size and link count). Messages are kept for 30 days, then removed, keeping only the sender, subject, time and score. An admin can delete one sooner.

In healthcheck.email

Open a domain, then its Inbox tab. Copy the intake address there, send or forward a message, and open it from the list. From a message you can add its headers to a case.