Skip to content

Email security · Prove and Defend in the Name Trust Lifecycle

Email spoofing protection

Email spoofing protection makes it hard for anyone else to send email as your domain. It relies on three DNS records: SPF, DKIM and DMARC. CertPing checks all three on your domain, shows which pass, and gives you the exact DNS record to add when one is missing or too weak, so receiving servers can reject or quarantine mail that impersonates you.

Last updated

A cream envelope closed with a navy wax seal
Email securitySPF, DKIM and DMARC1 to fix
  • SPFv=spf1 mx -allPass
  • DKIMs1._domainkeyPass
  • DMARCp=noneWeak
Record to addTXT _dmarc v=DMARC1; p=quarantineCopy
Illustration of CertPing. Names and data are examples.

Why domains get spoofed

Email was built without proof of who sent a message. Without SPF, DKIM and DMARC, anyone can send mail that claims to come from your domain.

Spoofed invoices and password resets that look like they came from you are a common start to fraud, and they damage trust in your real email.

What CertPing checks

  • 01

    SPF

    Sender Policy Framework lists the servers allowed to send email for your domain. CertPing checks that the record exists and is valid.

  • 02

    DKIM

    DomainKeys Identified Mail adds a cryptographic signature to your messages. CertPing checks that your domain publishes DKIM keys.

  • 03

    DMARC

    DMARC tells receiving servers what to do with mail that fails SPF and DKIM. CertPing checks the policy and whether it is strong enough to stop spoofing.

  • 04

    The record to fix it

    When a record is missing or too weak, CertPing shows the exact DNS record to add.

How the CertPing email security check works

  1. 1

    Enter your domain

    CertPing reads the public SPF, DKIM and DMARC records for the domain.

  2. 2

    See what passes

    Each record is marked as passing, missing or too weak.

  3. 3

    Add the suggested record

    Copy the DNS record CertPing gives you into your DNS. If the domain uses CertPing DNS, you edit it on the same page.

  4. 4

    Check again

    Run the check again to confirm the new record is live.

What you get

  • A pass, missing or weak result for SPF, DKIM and DMARC.
  • The exact DNS record to add for each gap.
  • One place to see email authentication next to the domain, DNS and certificates.

Limits and what you need to do

  • CertPing checks your records and tells you what to add. You publish the records in your DNS.
  • DMARC enforcement is carried out by receiving mail servers, not by CertPing.
  • These records protect your exact domain. Look-alike domains are covered by CertPing Anti-Phishing.

Email security questions

Something else? Talk to us.
01What are SPF, DKIM and DMARC?

SPF lists the servers allowed to send email for your domain, DKIM signs your messages, and DMARC tells receiving servers what to do with mail that fails those checks. CertPing checks all three and gives you the DNS record to add when one is missing or too weak.

02How do I stop someone spoofing my email domain?

Publish SPF and DKIM records for every service that sends your mail, then publish a DMARC policy of quarantine or reject. CertPing checks each record and gives you the exact record to add.

03Does CertPing enforce DMARC?

No. Receiving mail servers enforce DMARC by following the policy your domain publishes. CertPing checks that the policy exists and is strong enough, and gives you the record to fix it.

04Do I need to host my DNS with CertPing?

No. You can add the suggested records at any DNS provider. If your domain uses CertPing managed DNS, you can edit the records on the same page as the check.

05Does email security stop look-alike domains?

No. SPF, DKIM and DMARC protect your exact domain. Domains that imitate yours are detected by CertPing Anti-Phishing.

Your name, protected.

Domains, DNS, SSL certificates, email security and phishing detection, in one dashboard.