Email Checker

Check your email domain and find out why your mail goes to spam.

Type your email address or your domain name. We run a free SPF, DKIM, DMARC and MX check and test that your mail server answers. Then we tell you who hosts your email and what is sending your messages to spam.

We never touch a mailbox. Public records only.

Rated 5.0 on Google and Yelp

The report

Find why your email goes to spam

Each check is marked good, worth fixing or a problem. You get the records ready to copy and the fixes in the order to make them.

hansonplumbing.com
Finding the mail servers
Email provider
Google Workspace
Grade D
Every check we ran
Mail serversGood5 mail servers published, all pointing at Google Workspace, and every one of them resolves.
SPFGoodSPF is published and healthy.
DKIMUnclearWe could not find a DKIM key, and there is no way to prove one is not there.
DMARCProblemNo DMARC record. Nobody is told what to do with mail that fails the other checks.
HardeningWorth fixingNone of the optional hardening is switched on.
Fix these first
DMARC is missing
Without DMARC, a forged message that fails SPF and DKIM is still delivered. It is also now a requirement for bulk senders at Gmail and Yahoo.
No DKIM signature we could find
Unsigned mail is easier to forge and easier for receivers to distrust, and DMARC leans on DKIM to survive forwarding. Worth confirming in your mail provider's admin console, because a custom selector name would hide a key from us.

How it works

How email authentication works

Before your invoice reaches a customer's inbox, their mail server looks up three records on your domain. SPF lists who may send your mail. DKIM signs each message. DMARC says what to do when either check fails. We read all three, plus the MX records that bring replies back to you.

Sent

Invoice 1042

From
office@hansonplumbing.com
To
a customer on Gmail

Thanks for having us out on Tuesday. Your invoice is attached.

Invoice-1042.pdf

Signed on the way out

DKIM-Signature:
d=hansonplumbing.com; s=google

Checked by the customer's mail server

  1. SPF

    Is the server that sent this on the domain's list?

    Reads hansonplumbing.com

    Google's servers are listed

  2. DKIM

    Does the signature match the key the domain publishes?

    Reads google._domainkey.hansonplumbing.com

    Signature matches the key

  3. DMARC

    Did SPF or DKIM pass for the From address, and what happens to mail that fails?

    Reads _dmarc.hansonplumbing.com

    Passes, the policy is read

Where it lands

  • Inbox

    SPF or DKIM passes for the From domain

  • Spam folder

    Both fail and the policy says quarantine

  • Bounced

    Both fail and the policy says reject

With p=none, or no DMARC record at all, the receiver decides on its own.

Replies coming in

Senders read the MX records on hansonplumbing.com and deliver to the lowest number first: MX 1 aspmx.l.google.com, then the four Google backups.

How a receiving server checks a message: SPF in RFC 7208, DKIM in RFC 6376, DMARC in RFC 7489, delivery by MX in RFC 5321.

What we check

Check the records for email delivery

Each check reads the record the way a receiving mail server does and tells you what it means for your mail.

Count SPF lookups

Your SPF record can point to other companies' records, and each one costs a lookup. Receivers allow ten and fail SPF on the eleventh. We follow every include and give you the real count.

Check for duplicate records

A second SPF record makes every SPF check fail. The report flags it and says to merge them.

Name your email provider

When the record leaves out the company that runs your mail, the report names the one missing.

The record on hansonplumbing.com

v=spf1 include:_spf.google.com include:servers.mcsv.net include:email.freshdesk.com ~all

Three includes on the top line, and what each one pulls in

  • _spf.google.comGoogle Workspace

    +1
  • servers.mcsv.netMailchimp

    +1
  • email.freshdesk.comFreshdesk

    +1
    • sendgrid.net

      +1
      • ab.sendgrid.net

        +1
    • fdspfus.freshemail.io

      +1
    • fdspfeuc.freshemail.io

      +1
    • fdspfind.freshemail.io

      +1
    • fdspfaus.freshemail.io

      +1

9 of 10 lookups used

an 11th fails SPF

Each include as its provider published it on November 8, 2026, counted the way the report counts. The limit of 10 is RFC 7208, section 4.6.4.

Find your DKIM keys

A DKIM key only answers when asked by its exact name, called a selector. We ask for the names your provider documents, then the 18 that mail and marketing platforms use, and report how strong each key is.

Check which platform signs your email

A newsletter tool's key only signs the newsletter. For Microsoft 365, Proton Mail and Fastmail, the report checks for the provider's own key.

Flag short DKIM keys

Keys under 1024 bits are flagged, because some receivers reject them.

Find custom DKIM names

Google lets an admin name a selector anything. When none of the 19 names answer, the report marks DKIM unclear and says why.

hansonplumbing.com
DKIM, read from public DNS
Selector names asked
googledefaultdkimmailsmtps1s2k1k2k3mandrillsendgridpmhs1hs2mailjetsibzendesk1everlytickey1
DKIMGood
1 signing key published, so outgoing mail can be signed.
google._domainkey (rsa 2048-bit) via Google Workspace
TXTv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…

Sample: hansonplumbing.com with DKIM switched on. The 19 names are the report's own list for a Google Workspace domain.

Check your DMARC policy

We check that you publish a DMARC policy, what it tells receivers to do with mail that fails and whether its reports reach anyone.

Check where DMARC reports go

DMARC sends daily reports to the rua address in the record. With no address the reports go nowhere, and we flag it.

Spot partial DMARC policies

A pct value under 100 applies the policy to only part of the failing mail. The report gives the number.

  1. Start here

    p=none

    A forged invoice is delivered, and reported to you

    Monitor only. The reports arrive and nothing is blocked.

  2. A month later

    p=quarantine

    A forged invoice is sent to the spam folder

    Enforcing, once the reports show only your own senders.

  3. Strictest

    p=reject

    A forged invoice is refused before delivery

    Mail failing the checks is rejected outright.

The first record to publish, at _dmarc.hansonplumbing.com

v=DMARC1; p=none; rua=mailto:dmarc@hansonplumbing.com

rua is the address the daily reports go to.

Policies as RFC 7489, section 6.3 defines them. The steps between them are the report's own advice.

Find who runs your email

We match your mail servers against 35 providers, filters, forwarders and web hosts. When a security filter sits in front, we look behind it for the mailboxes your team signs in to.

Where you sign in

The report links to your provider's sign-in page, for when the person who set it up has moved on.

Who holds the DNS

The company that runs your DNS. Every change on this page is made in that account.

Email provider for hansonplumbing.com
Reading the mail servers
The order your mail servers are tried
1aspmx.l.google.com
5alt1.aspmx.l.google.com
5alt2.aspmx.l.google.com
10alt3.aspmx.l.google.com
10alt4.aspmx.l.google.com
Google’s mail servers, so the mailboxes are Google Workspace. No filter sits in front of them.
Where changes get made
Where you sign inadmin.google.com
Who holds the DNSCloudflare (aria.ns.cloudflare.com)

hansonplumbing.com: Google Workspace mail, with DNS at Cloudflare.

Worked example

Stop losing email to spam

Hanson Plumbing's customers kept asking where their invoices were. Here is what the check found, what it meant, and the two records that fixed it.

1

What the check found

Mail servers and SPF passed. No DMARC record sat at _dmarc.hansonplumbing.com, and none of the 19 selector names returned a DKIM key. Score 67, Grade D.

2

Why it matters

Nothing in Hanson's mail proved it came from Hanson's own account, and receivers had no instruction for mail that fails. Gmail requires SPF or DKIM from every sender. Anyone who sends 5,000 or more messages a day to Gmail addresses needs SPF, DKIM and DMARC together.

3

Two records to add

The report names Cloudflare as the DNS host, so both changes happen there. In the Google Admin console, open Apps, Google Workspace, Gmail, Authenticate email, publish the record it gives at google._domainkey, and press Start authentication.

Then add a first DMARC record at _dmarc, with a reporting address:

v=DMARC1; p=none; rua=mailto:dmarc@hansonplumbing.com

Checked again, the domain scores 91, Grade A. After a month of clean reports, moving to p=quarantine takes it to 97.

DNS records
hansonplumbing.com, at Cloudflare
MX@1 aspmx.l.google.com
TXT@v=spf1 include:_spf.google.com include:servers.mcsv.net include:email.freshdesk.com ~all
TXTgoogle._domainkeyv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…
TXT_dmarcv=DMARC1; p=none; rua=mailto:dmarc@hansonplumbing.com
Email health, Grade DMail is flowing, but 1 thing here is costing you inbox placement.

Scores from the report's own scoring. Gmail's rules from its Email sender guidelines.

After the report

Get your email back in the inbox

  1. On your own

    Change the record

    The full report gives you the records ready to copy. It also names the company that holds your DNS, where the change gets made.

  2. With our team

    Send us the report

    We tell you what to change and who has to change it. On sites we look after, you email our team and we handle it.

    See website maintenance
  3. In Venbit Intelligence

    Get a push for every form

    Venbit Intelligence sends a push with the person's name the moment a form lands. If the email goes missing, you still get the lead.

    See the Inbox

Questions

Questions about the email check

Is it free?

Yes, with no trial and no card to enter. We fix email records for clients most weeks. If the check helps you, you will remember us.

Do you read my email?

No, and we could not if we wanted to. Everything comes from public DNS records. Every mail server reads the same ones before it delivers a message to you. We open no mailbox and log in to nothing.

What is the hello you send my mail server?

One connection on the standard mail port. We say hello (EHLO) and hang up (QUIT). That is the first step of any email delivery, with no email sent. It tells us the server is up and whether it offers encryption.

You said no DKIM key. Are you sure?

Only when we know your provider. DKIM is the signature your provider adds to each email. Its record sits under a name called a selector, and nobody can list selectors. We check the ones your provider documents plus the common defaults. When we know your provider and none of its selectors answer, that is a real finding. When we do not know the provider, the report says so.

Why does my mail go to spam when everything says green?

Records come first, and they are one part of it. Your sending reputation, your list, your content and how much you send count too. Fix the records first. A new subject line will not fix a missing DKIM key.

Can I check a domain I do not own?

Yes. These records are public so any mail server can read them. Checking a supplier before you trust their invoice is a smart move.

What do you do with my email address?

You use it to unlock the report, and we send you a copy. Nothing follows it, and your address is never sold or shared.

Want to know who holds the domain itself and when it renews?Run the Domain LookupSee what the website is built with

Where Venbit comes in

Get help fixing email that goes to spam

When your invoices land in a customer's spam folder, start with your DNS records, the public settings on your domain. One missing record is enough. Venbit has fixed this for small businesses since 2011. Send us the report and we will tell you what to change and who has to change it.

Or call us at (425) 314-1415

Try another free tool