home

Free domain and email deliverability check: Land in the inbox.

For anyone sending donor, event or program email from their own domain. Type it in and see whether receivers can trust your email, and whether your certificate or domain is about to lapse. Every result comes with what it means and what to do.

The part after the @ in your email address. A web address or email address works too.

If you know it. Otherwise we’ll try the common ones.

How it works

  1. Type your domain.

    The part after the @ in your email address. A web address or a whole email address works too; we’ll take the domain from it.

  2. We read the public records.

    Your SPF, DKIM and DMARC records, your mail servers and nameservers, your website’s certificate and your domain’s registry entry. All of it is public. Nothing is stored.

  3. Fix what’s red.

    Each result says what it means and what to do, in plain words you can forward to whoever manages your domain. Print it, save it as a PDF, or copy it as text.

Questions

Deliverability, explained.

  • Three DNS records that prove your email is really from you. SPF lists the services allowed to send as your domain. DKIM adds a signature to each message that receivers check against a public key. DMARC tells receivers what to do when a message fails both, and sends you reports about it.

  • Since February 2024, everyone sending to Gmail or Yahoo needs SPF or DKIM. Bulk senders (Google’s line is 5,000 or more messages a day to Gmail) need both, plus a DMARC record of at least p=none, a From address that aligns with SPF or DKIM, one-click unsubscribe for marketing email, and a spam rate under 0.3%.

  • DKIM keys live under a name the sending service picks, called a selector, and there’s no way to list them from outside. We try the common ones. If yours isn’t among them, find it in an email you sent: open the original or the source and look for DKIM-Signature. The s= value is your selector. Run the check again with it.

  • No, but it means the setup isn’t what’s stopping it. Receivers also weigh your sending reputation, how many people mark you as spam, and what’s in the message. This check covers the part you control in DNS.

  • It’s a good first step and meets the Google and Yahoo minimum. It only watches, though: forged email still gets delivered. Read the reports for a few weeks, make sure your real senders pass, then move to p=quarantine and later p=reject.

  • Often minutes, sometimes up to a day or two, depending on the record’s TTL. We keep each result for ten minutes, so wait a little before checking again.

  • No. The check runs on our server because browsers can’t read DNS records, but nothing is stored. Each result is held in memory for ten minutes so a repeat check is quick, then it’s gone.

Sources

Sender requirements last checked October 23, 2026.

Want a hand fixing what it found? Talk to us, or see more odds and ends.