Samprix

Is your email set up right?

Check SPF, DKIM, DMARC and MX in one go. Get a score, see whether you meet Gmail’s, Yahoo’s and Microsoft’s rules, and a plain-English fix for every problem.

  • Live DNS lookup
  • Results in seconds
  • No sign-up
  • Free
C 75 / 100

Email health report

github.com needs a few fixes

  • 0 problems
  • 2 warnings
  • 7 passed
Run again

Gmail, Yahoo & Microsoft basics

  • A valid SPF record
  • A DKIM key published
  • A DMARC record (p=none or stricter)
What they require

Fix these first

  1. 1

    SPF 10 of 10 DNS lookups used

    Close to the limit. Adding one or two more services will make SPF fail; a provider changing its own include can push it over without you changing anything.

  2. 2

    DKIM selector1, k1, smtpapi, cm: 1024-bit key

    1024-bit keys still work, but 2048 bits is the current recommendation. Rotate to a 2048-bit key when you can.

Every check

Mail servers (MX) Good Details
  • OK:One mail server

    Email is handled by Microsoft 365.

Full Mail servers check
SPF Needs attention Details
  • Warning:10 of 10 DNS lookups used

    Close to the limit. Adding one or two more services will make SPF fail; a provider changing its own include can push it over without you changing anything.

  • OK:Ends with ~all (soft fail)

    Servers not listed get a soft fail. With DMARC in place this is the usual choice; -all is stricter.

  • OK:One SPF record published

Full SPF check
DKIM Needs attention Details
  • Warning:selector1, k1, smtpapi, cm: 1024-bit key

    1024-bit keys still work, but 2048 bits is the current recommendation. Rotate to a 2048-bit key when you can.

  • OK:google, k2, k3, s1, s2, zendesk1, zendesk2: 2048-bit RSA key

Full DKIM check
DMARC Good Details
  • Note:Failure reports requested (ruf=)

    Few providers send them any more (Gmail doesn’t), for privacy reasons. Harmless, but don’t rely on them.

  • OK:Policy is quarantine

    Mail that fails DMARC goes to spam. p=reject, the strictest setting, blocks it outright.

  • OK:Reports go to dmarc@github.com

  • OK:One valid DMARC record published

Full DMARC check

Advertisement

The four records behind email delivery

  • MX tells other servers where to deliver mail for your domain. Wrong or missing MX records mean mail to you bounces.
  • SPF lists the servers allowed to send as your domain.
  • DKIM publishes the key your email service signs messages with, proving they weren’t forged or changed.
  • DMARC tells receivers what to do when a message fails SPF and DKIM, and sends you reports. It’s what actually stops spoofing.

Since 2024, Gmail and Yahoo require all three of SPF, DKIM and DMARC from bulk senders, and Microsoft followed in 2025 for Outlook.com. Mail that doesn’t meet the rules is increasingly rejected rather than just sent to spam. See the full requirements and how the three records fit together.

Fix in this order

  1. Make sure MX points at your real email provider.
  2. Publish one SPF record that includes every service that sends for you.
  3. Turn on DKIM signing with your own domain in each of those services.
  4. Publish DMARC at p=none with a report address, read the reports, then tighten it.

Did this tool do what you needed?

All tools