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

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

A+

atlassian.com

95 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.

Starting score
100
SPFEnds with ~all (softfail).
-5
Your score
95

  • SPF

    -5Pass
    • -5

      Ends with ~all (softfail).

      A softfail asks receivers to accept mail from unlisted senders but flag it, so spoofed messages can still reach the inbox.

      How to fix: Move to -all after confirming that all of your senders are included, so unauthorized mail is rejected.

    DNS lookups6 / 10
    v=spf1 ip4:54.85.255.245 ip4:54.241.191.3 include:_spf.google.com include:cust-spf.exacttarget.com include:spf-001d9801.pphosted.com include:amazonses.com include:spf1.atlassian.com include:spf3.atlassian.com ip4:54.71.147.74 ip4:54.71.63.106 ip4:54.70.13.32 ~all
    allQualifier
    ~

  • DKIM

    Pass

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

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

    selectors
    google, s1, s2, mandrill, smtpapi
    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; fo=1; pct=100; adkim=r; aspf=r; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc-rua@abuse.atlassian.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com,mailto:dmarc-ruf@abuse.atlassian.com
    policy
    reject
    subdomainPolicy
    reject
    pct
    100
    rua
    mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc-rua@abuse.atlassian.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
    mxb-001d9801.gslb.pphosted.com (10), mxa-001d9801.gslb.pphosted.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
    67.231.152.116, 208.84.65.201
    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

    • Zone is signed but DNSSEC is not active.

      Your zone publishes DNSKEY records, but the parent has no DS record, so there is no chain of trust and resolvers cannot actually validate your domain.

      How to fix: Add the DS record from your DNS provider at your registrar to complete the chain of trust and activate DNSSEC.

    algorithm
    ECDSAP256SHA256
    signatureExpiry
    2026-07-06T18:00:00Z

  • 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://vmc.digicert.com/ad1c2acd-2d54-462c-a78d-57351f374742.svg; a=https://vmc.digicert.com/ad1c2acd-2d54-462c-a78d-57351f374742.pem
    logo
    https://vmc.digicert.com/ad1c2acd-2d54-462c-a78d-57351f374742.svg
    vmc
    https://vmc.digicert.com/ad1c2acd-2d54-462c-a78d-57351f374742.pem

This report looks at the email authentication posture of atlassian.com as it appears in public DNS today. Software platforms send a constant stream of transactional mail, so the records that prove those messages are genuine directly affect whether customers receive them.

How to read the grade

Everything above is computed live from the records atlassian.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 atlassian.com and is provided for informational and educational purposes only. SPFWise is not affiliated with, endorsed by, or connected to the owner of atlassian.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.