Deliverabilityfree audit

Audit in progressAudit complete

Free · no sign-up

Do your emails arrive?

We read your domain’s public settings: who can send email in your name, and whether your messages avoid spam.

Nothing is changed. No email needed.

  • Who can send in your name (SPF)
  • Signature (DKIM)
  • Rejection rule (DMARC)
Right now, somewhere

The “From:” field of an email is filled in freely, like the sender on the back of an envelope. Here’s your customer’s inbox, before and after your domain says who’s allowed to write in its name.

Your customer receives your reminder: invoice #2041.

A stranger sends the same invoice, signed with your address, with his bank details.

In the list, nothing tells them apart: same name, same address.

Paid. Into the stranger’s account.

You set your rules: three lines at your domain registrar.

The same stranger tries again. The inbox checks the signature: it isn’t there.

Spam. Your customer never opens it, and you know who tried.

Your real reminder now carries the “verified” mark.

What sorts this inbox takes three lines at your domain registrar.

Today, nothing in your customer’s inbox shows this message is fake. Your domain may be in this position.

What decides where your messages land

Gmail, Outlook, Yahoo and iCloud read the same three settings to sort your email: allowed servers (SPF), signature (DKIM) and the rule for fakes (DMARC). Each draws its own conclusions.

Questions we get asked
Can someone really send email in my name?

Yes, and anyone can do it. The “From:” field of an email is filled in freely, like the sender on the back of an envelope. Only three records in your domain let the recipient’s server refuse a fake. If they’re missing, or set up but not enforced, the fake gets through.

I have nothing to hide. Why should I care?

You’re not the target: your customers are. The most common case is the fake invoice: a message that seems to come from your accounting, announcing new bank details. The customer pays, and it’s your name that did the work.

What does this audit check?

Checks of your domain in the internet’s public directory (DNS), scored out of 100. Who can send in your name, what a server should do with a fake, whether your messages are signed, whether a backup server receives your mail, whether transport is encrypted. Blocklists are checked too, outside the score. No message is sent, nothing is left on your site.

My signature isn’t detected. Is that bad?

Not necessarily. The signature is filed under a name chosen by the sender, and that name can’t be read from outside. When we can’t find it, we write “not detected” and this check leaves the calculation, instead of docking points for something we couldn’t measure.

Do I need a contractor to fix this?

Rarely. These are lines to add wherever your domain name is managed, often three. The only delicate part is switching the policy to enforcing without blocking a legitimate sending service: that’s done in stages, by reading the reports.

Audit in progress

    Audit of example.com

    0,0 s
    0/ 100
    Reading your site

    Your score is building.

    Each check adds the points it earns, and shows the ones you’re missing.

    0points out of 100
    Reading your site Connecting to the site
    Connection Connecting to the site
    Audit details

    PricingFAQLegal noticePrivacyTermsContact us