See what this message can prove
An Inbox Reality Check tests what a real message can prove, not just what your DNS says. Send one (or paste it) and we'll verify DKIM, DMARC alignment, and the evidence available on this path.
Easiest, and the only one that works on your phone. Send any email from the account you want to test — we read the headers and email your report back.
results@report.hireamino.com. We're a brand-new sender, so check your spam folder — if it landed there, mark it “Not spam.” (That helps us, and it's a live demo of exactly what we measure.)
On a desktop? Paste a message's full source.
Your result appears right here — nothing is emailed.
Have the email saved as a .eml? Drop it in and we'll read it.
Your result appears right here — nothing is emailed.
Read-only — we read the headers, never the message body, and never change anything you send.
Want this watched for you — for free?
Monitor your domain for free →Daily deliverability checks — we email you only when something changes.
Inbox Reality Check FAQ
How does this work?
You send any email to our probe address from the account or system you want to test. We cryptographically verify DKIM, determine whether aligned DKIM proves DMARC, inspect SPF record health, and read the visible routing, TLS, and bulk-sender unsubscribe headers. SPF needs SMTP-time receiver evidence that this Worker does not receive, so the scorecard labels the per-message SPF result unavailable instead of guessing. We discard the message after processing and don't keep the body.
Do you actually verify my DKIM signature, or just look for one?
We verify it. We fetch your public key from DNS and check the signature cryptographically (RFC 6376 — RSA and Ed25519), recomputing the header and body hashes the same way a receiving mail server does. That matters: a check that only looks for a DKIM-Signature header and confirms the domain matches will report a forged or broken signature as passing. Raw Authentication-Results headers are not trusted; DKIM passes only when the maths verifies.
Why send an email instead of typing my domain?
A DNS check (like our /audit) tells you what your records say. A full message provides evidence DNS alone cannot: a DKIM signature we can verify, a sending IP we can check with forward-confirmed reverse DNS, and the route/TLS trace the message carries. Routing traces can be incomplete or modified, so the report labels them as visible evidence rather than a receiver verdict.
What's the difference from a DNS audit?
The audit reads public DNS. This reads a real send — and pulls your DKIM selector and sending IP out of the message, so we can confirm the actual signing key and reverse-DNS (things a DNS-only check can't do).
Can you tell me whether I'll land in the inbox or in spam?
No, and nothing that reads only your message can. Inbox placement is decided per-recipient by the receiving provider using your sending reputation, their user's engagement history and signals we have no access to. What we can tell you is whether your authentication is technically correct and provable — which is the part you control, and the part that gets you rejected outright when it's wrong. Anyone promising a placement prediction from headers alone is guessing. To see actual placement you need seed inboxes at each provider, which this tool doesn't use.
Do you store my email?
We keep a short record of the result — your sending domain, your email address, and the scorecard summary — for 30 days, to run the service and the free-usage limit (5 checks per 30 days). We never store your message body, and the record is deleted after 30 days. See our Privacy page for details.
How do I get a message's full source to paste or upload?
Gmail (desktop): open the message → ⋮ (More) → Show original → Copy to clipboard (to paste), or Download original to save a .eml to upload. Outlook (desktop): open the message → File → Properties and copy the Internet headers, or File → Save As → .eml to upload. Apple Mail: select the message → File → Save As → Raw Message Source (.eml).