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 brevo.com

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

A+

brevo.com

100 out of 100

Scanned: Jul 6, 2026, 1:22 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

    • 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 lookups2 / 10
    v=spf1 include:_spf.google.com include:mail.zendesk.com -all
    allQualifier
    -

  • DKIM

    Warning

    • A wildcard DKIM record is published.

      A wildcard (*._domainkey) returns the same key for every selector, so we cannot tell which selectors are really in use, and any selector name will appear to validate. Confirm this is intentional.

      How to fix: Publish a specific record for each selector you actually sign with, and remove the wildcard unless you have a clear reason for it.

    selectors
    * (wildcard)
    Read the DKIM guide

  • 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; sp=reject; rua=mailto:rua@dmarc.brevo.com;
    policy
    reject
    subdomainPolicy
    reject
    pct
    100
    rua
    mailto:rua@dmarc.brevo.com
    adkim
    r
    aspf
    r

  • MX

    Pass

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

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

    mxHosts
    aspmx.l.google.com (1), alt1.aspmx.l.google.com (5), alt2.aspmx.l.google.com (5), alt4.aspmx.l.google.com (10), alt3.aspmx.l.google.com (10)
    mxCount
    5

  • 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
    108.177.125.27, 192.178.211.27, 192.178.158.26
    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

    Pass

    • BIMI is set up.

      Your BIMI record is valid, DMARC is enforced, and a Verified Mark Certificate is present, so supporting inboxes can show your logo.

    v=BIMI1; l=https://bimi.brevo.com/logo.svg; a=https://bimi.brevo.com/logo.pem;
    logo
    https://bimi.brevo.com/logo.svg
    vmc
    https://bimi.brevo.com/logo.pem

Below is a live breakdown of how brevo.com authenticates the mail it sends. Providers in the email industry are held to a high bar here, and their public records offer a practical example of SPF, DKIM, and DMARC in use.

How to read the grade

Everything above is computed live from the records brevo.com publishes right now. A strong result means SPF authorizes the correct senders, DKIM signs outgoing mail with a valid key, and DMARC sets a policy that instructs receivers on how to handle failures. Where a check is weak, the report shows the exact record involved so the gap is easy to understand.

About this report

This report is generated from publicly available DNS records for brevo.com and is provided for informational and educational purposes only. SPFWise is not affiliated with, endorsed by, or connected to the owner of brevo.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.