BetaSPFWise is in beta, and every feature is free until it ends. More information after you sign up.
SPFWise
How it worksWhat we checkPricingFAQGuides

Email Authentication Report for wordpress.com

A live look at how wordpress.com configures SPF, DKIM, DMARC, and transport security, with the grade explained.

A+

wordpress.com

100 out of 100

Scanned: Jul 6, 2026, 1:13 PM

Why this score

The score starts at 100. Every issue below subtracts points based on how much it hurts your deliverability or lets someone spoof you.

Nothing is lowering your score. Every live check passed cleanly.

  • SPF

    Pass

    • Close to the DNS lookup limit (8 of 10).

      You are using 8 of the 10 allowed DNS lookups. Adding one more sender could push SPF over the limit and break it.

      How to fix: Flatten some includes into ip4 or ip6 ranges to leave headroom below the limit of 10.

    • Ends with -all (hardfail).

      A hardfail tells receivers to reject any sender that is not listed. This is the strongest and recommended setting.

    • SPF is present and correctly configured.

      A single SPF record was found, it stays within the DNS lookup limit, and it ends with a strong all qualifier.

    DNS lookups8 / 10
    v=spf1 include:_spf.automattic.com include:servers.mcsv.net include:_spf-wwd.automattic.com include:mail.zendesk.com include:sendgrid.net include:145630858.spf04.hubspotemail.net include:amazonses.com -all
    allQualifier
    -

  • DKIM

    Pass

    • DKIM is set up (6 valid selector(s) found).

      At least one valid signing key was found, so your outgoing mail can be signed and verified by receivers.

    selectors
    k1, k2, k3, mandrill, zendesk1, zendesk2
    keyType
    rsa
    keyBits
    2048

  • DMARC

    Pass

    • Policy is p=reject (strongest).

      Reject tells receivers to refuse any mail that fails authentication, the strongest protection against spoofing.

    • Aggregate reporting is enabled.

      A rua address is set, so you receive daily reports showing every source that sends as your domain.

    • DMARC is present and enforced.

      A valid DMARC record was found with an enforcing policy, so receivers act on mail that fails authentication.

    v=DMARC1; p=reject; pct=100; rua=mailto:0bqp2jnw@ag.dmarcian.com; ruf=mailto:0bqp2jnw@fr.dmarcian.com;
    policy
    reject
    subdomainPolicy
    reject
    pct
    100
    rua
    mailto:0bqp2jnw@ag.dmarcian.com
    adkim
    r
    aspf
    r

  • MX

    Pass

    • MX is configured (2 mail server(s)).

      Your domain has MX records and every listed mail server resolves to an IP address, so it can receive mail.

    mxHosts
    mx-dfw.automattic.com (10), mx-ams.automattic.com (10)
    mxCount
    2

  • Blacklist

    Pass

    • Not on any checked blocklist.

      Your mail server IPs were not found on the public blocklists we checked. Reputation can change, so it is worth monitoring over time.

    ipsChecked
    192.0.84.151, 195.234.109.226
    blocklists
    bl.spamcop.net, dnsbl.sorbs.net

Optional enhancements

Advanced, nice-to-have features. Setting these up (or not) does not change your grade.

  • DNSSEC

    Optional

    • DNSSEC is not enabled.

      DNSSEC is optional, but it protects against DNS spoofing by letting resolvers confirm your records are authentic. Most domains still do not use it.

      How to fix: If your DNS provider and registrar support it, enable DNSSEC to protect your domain from DNS tampering.

  • MTA-STS

    Optional

    • MTA-STS is not set up.

      MTA-STS is optional but recommended. It tells sending servers to require TLS when delivering mail to you, which blocks downgrade and man-in-the-middle attacks on your inbound mail.

      How to fix: Publish a _mta-sts TXT record and host a policy at https://mta-sts.<yourdomain>/.well-known/mta-sts.txt with mode enforce.

    Read the MTA-STS guide

  • TLS-RPT

    Optional

    • TLS reporting (TLS-RPT) is not set up.

      TLS-RPT is optional. It asks receivers to send you reports when TLS fails while delivering your mail, which is how you catch MTA-STS or certificate problems before they hurt delivery.

      How to fix: Publish a _smtp._tls TXT record with v=TLSRPTv1 and a rua address, for example rua=mailto:tlsrpt@yourdomain.

    Read the TLS-RPT guide

  • BIMI

    Optional

    • BIMI has no Verified Mark Certificate.

      Your BIMI record has no a= (VMC) tag. Gmail and Apple Mail require a VMC to show your logo, so those inboxes will not display it even though the record is otherwise valid.

      How to fix: Obtain a Verified Mark Certificate for your trademark and add it with the a= tag to reach Gmail and Apple Mail.

    v=BIMI1; l=https://wordpress.com/i/bimi/wpcom.svg; a=;
    logo
    https://wordpress.com/i/bimi/wpcom.svg
    vmc
    Read the BIMI guide

This report reviews the email authentication records published for wordpress.com. Media and reference sites send newsletters and account mail to large audiences, so the records that authenticate that mail have a direct effect on delivery.

The checks behind the grade

The score above reflects the public DNS records for wordpress.com at the time of the scan. SPF declares which servers may send mail for the domain, DKIM signs each message so tampering can be detected, and DMARC combines both with a published policy. Additional transport-security records raise the grade by securing the delivery path between mail servers.

About this report

This report is generated from publicly available DNS records for wordpress.com and is provided for informational and educational purposes only. SPFWise is not affiliated with, endorsed by, or connected to the owner of wordpress.com. The records shown are the same ones any mail server can query, and the grade updates automatically as they change.

Want the same breakdown for your own domain? Run a free scan to get an identical grade along with the exact records to fix anything that is weak.

Check your own domain

Run a free scan and get your grade with the exact records to fix.

Scan a domain

Guides to fix common issues

Email Compliance: CAN-SPAM, GDPR and CASL Basics

A plain-English guide to the three laws that govern commercial email: CAN-SPAM in the US, GDPR in the EU, and CASL in Canada, covering consent, identification, unsubscribe, penalties, and how compliance overlaps with deliverability.

Dedicated vs Shared IP for Sending Email

A practical guide to choosing between a dedicated and a shared sending IP, weighing volume, reputation control, warmup burden, and cost, with a clear decision path.

Phishing vs Spoofing: What Is the Difference?

Spoofing is the technique of forging a sender identity; phishing is the fraud it enables. This guide explains the difference, how they overlap, and which defenses stop each.