Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Atlassian

atlassian.com
🏆Rank #563 🏷 SaaS 🇦🇺Australia ✓ Inbox 98%

Atlassian uses Salesforce MC for marketing email and Amazon SES for transactional/notifications. They rank #563 in the Tranco list of most-popular domains. We've also observed sends via 3 other providers: Bloomreach, Keap, Deployteq. Email goes out from 46 different subdomains. Their email authentication setup is solid (score 100/100).

Marketing ESPSalesforce MC
Transactional ESPAmazon SES
Total observations1,061
Active days50
Avg per active day21.2
Last activity📬 Active · today
Cadence~weekly

Other technologies

Non-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.

HTML builder Stripo
Compare Atlassian with another brand:

Email setup 100/100

Authentication signals observed in this brand's emails. SPF, DKIM and DMARC are the standard sender-authentication stack — see the DMARC policy below for whether spoofing is actually blocked or just monitored. One-click unsubscribe meets Google & Yahoo's bulk-sender requirements.

Strong email setup
Authentication is in good shape — SPF, DKIM, and DMARC enforcement all configured.
100/100
SPF
pass
DKIM
pass
DMARC
pass (reject)
BIMI
verified VMC
Unsubscribe
one-click
SPF lookups 7/10

SPF / DKIM / DMARC above reflect the last 10 emails we've observed. DMARC policy is read live from DNS.

Authentication

DMARC reports sent to proofpoint.com. Policy p=reject means receivers actively block or quarantine spoofed mail.

SPF alignment: 99% of observed emails use an aligned return-path (atlassian-bounces.atlassian.net, bounce.e.atlassian.com, atlassian-bounces.atlassian.com); the rest use third-party paths (benchmarkemail.com) where DMARC has to rely on DKIM alignment.

DKIM alignment: all 781 observed emails sign with a domain aligned with atlassian.com (atlassian.net, e.atlassian.com, atlassian.com). DKIM authenticates the visible From — supports DMARC directly.

Brand visibility

VMC issued by: digicert.

Transport & deliverability

TLS: modern — 91% TLS 1.3 (across 401 sends).

Delivery: fast — 98% of emails in the last 7 days arrive in under 10 seconds (across 158 sends).

Other ESPs detected

Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).

Bloomreach 19 Keap 1 Deployteq 1

Confirmed senders

ESPs we've seen sending email for this brand. Green = confirmed by SPF, sender IP rDNS, or known infra pairing (label shows the source). Grey = observed but not yet confirmed by SPF or PTR.

Amazon SES ✓ confirmed Salesforce MC ✓ confirmed Bloomreach ✓ via SendGrid

Other SPF authorizations

ESPs this brand has authorized in their SPF record. We confirm them with a green ✓ only after seeing recurring use (3+ emails across 2+ days). Until then they stay here — either we haven't observed any email yet, or we've seen a handful but not enough to call them a regular sender for the brand.

Google Workspace Proofpoint SendGrid SparkPost

Probed: atlassian.com, atlassian-bounces.atlassian.net, bounce.e.atlassian.com, atlassian-bounces.atlassian.com, benchmarkemail.com, pragmawoo.atlassian.net, dartagnan.atlassian.net, antevenio.atlassian.net, percona.atlassian.net, vercom.atlassian.net, communicatorcorp.atlassian.net, rebrandly.atlassian.net

Where emails landed (Gmail)

Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.

FolderCountShare
inbox 842 98.5%
promotions 13 1.5%

Placement by ESP

Which ESP's emails are landing where. Sorted by spam % so problem senders surface first. Brands using one ESP for marketing and another for transactional often see very different placement profiles per ESP. Per-ESP folder data only started being captured recently — counts here may be smaller than the total above until backfill catches up.

ESP Emails Placement Inbox % Tabs % Spam %
Amazon SES 622
99.0% 1.0% 0.0%
Bloomreach 14
100.0% 0.0% 0.0%
Salesforce MC 111
93.7% 6.3% 0.0%
Keap 1
100.0% 0.0% 0.0%
Deployteq 1
100.0% 0.0% 0.0%

ESP activity over time

Apr 14 – Jun 30, 2026 · 64 days with sends

Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.

56 0 Amazon SES: 1 (2026-04-14)1Amazon SES: 12 (2026-04-18)12Amazon SES: 1 (2026-04-20)1Amazon SES: 1 (2026-04-21)1Bloomreach: 1 (2026-04-24)1Amazon SES: 8 (2026-04-27)8Amazon SES: 1 (2026-04-28)1Amazon SES: 2 (2026-04-30)2Salesforce MC: 1 (2026-05-02)1Amazon SES: 2 (2026-05-03)2Amazon SES: 14 (2026-05-04)Salesforce MC: 2 (2026-05-04)16Amazon SES: 7 (2026-05-05)Salesforce MC: 6 (2026-05-05)13Amazon SES: 33 (2026-05-06)Salesforce MC: 2 (2026-05-06)35Amazon SES: 8 (2026-05-07)Salesforce MC: 1 (2026-05-07)9Amazon SES: 10 (2026-05-08)10Amazon SES: 3 (2026-05-09)3Amazon SES: 1 (2026-05-10)1Amazon SES: 22 (2026-05-11)Salesforce MC: 3 (2026-05-11)25Amazon SES: 16 (2026-05-12)Salesforce MC: 4 (2026-05-12)20Amazon SES: 18 (2026-05-13)Salesforce MC: 10 (2026-05-13)28Amazon SES: 23 (2026-05-14)Salesforce MC: 1 (2026-05-14)24Amazon SES: 9 (2026-05-15)Salesforce MC: 2 (2026-05-15)Keap: 1 (2026-05-15)12Amazon SES: 3 (2026-05-16)3Amazon SES: 2 (2026-05-17)2Amazon SES: 17 (2026-05-18)Salesforce MC: 2 (2026-05-18)19Amazon SES: 25 (2026-05-19)Salesforce MC: 3 (2026-05-19)Bloomreach: 1 (2026-05-19)29Amazon SES: 21 (2026-05-20)Salesforce MC: 2 (2026-05-20)23Amazon SES: 11 (2026-05-21)Salesforce MC: 2 (2026-05-21)13Amazon SES: 10 (2026-05-22)Salesforce MC: 1 (2026-05-22)11Amazon SES: 2 (2026-05-23)2Amazon SES: 18 (2026-05-25)18Amazon SES: 16 (2026-05-26)Salesforce MC: 4 (2026-05-26)Bloomreach: 3 (2026-05-26)23Amazon SES: 11 (2026-05-27)Salesforce MC: 4 (2026-05-27)15Amazon SES: 13 (2026-05-28)Salesforce MC: 2 (2026-05-28)15Amazon SES: 14 (2026-05-29)Salesforce MC: 2 (2026-05-29)Bloomreach: 1 (2026-05-29)17Amazon SES: 2 (2026-05-30)2Amazon SES: 3 (2026-05-31)Salesforce MC: 2 (2026-05-31)5Amazon SES: 22 (2026-06-01)Salesforce MC: 3 (2026-06-01)25Amazon SES: 19 (2026-06-02)Salesforce MC: 1 (2026-06-02)20Amazon SES: 5 (2026-06-03)5Amazon SES: 23 (2026-06-04)Salesforce MC: 6 (2026-06-04)29Amazon SES: 36 (2026-06-05)Salesforce MC: 4 (2026-06-05)Bloomreach: 2 (2026-06-05)42Amazon SES: 14 (2026-06-08)14Amazon SES: 27 (2026-06-09)Salesforce MC: 2 (2026-06-09)Bloomreach: 2 (2026-06-09)31Amazon SES: 44 (2026-06-10)Salesforce MC: 6 (2026-06-10)Bloomreach: 6 (2026-06-10)56Amazon SES: 39 (2026-06-11)Salesforce MC: 4 (2026-06-11)Bloomreach: 2 (2026-06-11)45Amazon SES: 27 (2026-06-12)27Salesforce MC: 1 (2026-06-13)1Amazon SES: 1 (2026-06-14)1Amazon SES: 17 (2026-06-15)Salesforce MC: 2 (2026-06-15)19Amazon SES: 37 (2026-06-16)37Amazon SES: 32 (2026-06-17)Salesforce MC: 7 (2026-06-17)Deployteq: 1 (2026-06-17)40Amazon SES: 32 (2026-06-18)Salesforce MC: 3 (2026-06-18)35Amazon SES: 10 (2026-06-19)10Amazon SES: 2 (2026-06-20)2Amazon SES: 28 (2026-06-22)Salesforce MC: 12 (2026-06-22)40Amazon SES: 29 (2026-06-23)Salesforce MC: 4 (2026-06-23)33Amazon SES: 17 (2026-06-24)Salesforce MC: 1 (2026-06-24)18Amazon SES: 10 (2026-06-25)Salesforce MC: 2 (2026-06-25)12Amazon SES: 11 (2026-06-26)Salesforce MC: 4 (2026-06-26)15Amazon SES: 1 (2026-06-27)1Amazon SES: 1 (2026-06-28)1Amazon SES: 27 (2026-06-29)Salesforce MC: 8 (2026-06-29)35Amazon SES: 14 (2026-06-30)1404/1404/2204/3005/0805/1605/2406/0106/0906/1706/2506/30
Amazon SES Salesforce MC Bloomreach Keap Deployteq

Similar brands using Salesforce MC

Sending IPs

IP addresses atlassian.com has been observed sending from, and where their mail landed in Gmail.

IPHostnameObsPlacementReputation
136.147.141.72 mta.e.atlassian.com 45 4 Check →
136.147.143.2 mta3.e.atlassian.com 44 13 Check →
136.147.143.1 mta3.e.atlassian.com 44 8 Check →
76.223.147.139 c147-139.smtp-out.us-west-2.amazonses.com 5 Check →
76.223.147.140 c147-140.smtp-out.us-west-2.amazonses.com 3 Check →
216.221.175.223 g175-223.smtp-out.amazonses.com 3 Check →
216.221.175.239 g175-239.smtp-out.amazonses.com 2 1 Check →
76.223.147.141 c147-141.smtp-out.us-west-2.amazonses.com 2 Check →
76.223.147.134 c147-134.smtp-out.us-west-2.amazonses.com 2 Check →
216.221.175.142 g175-142.smtp-out.amazonses.com 2 1 Check →
216.221.175.199 g175-199.smtp-out.amazonses.com 2 2 Check →

Sending domains

DomainESPs detectedDelivery (7d)
antevenio.atlassian.netAmazon SES 136
e.atlassian.comSalesforce MC 134
kiloverse.atlassian.netAmazon SES 127
mi-team.atlassian.netAmazon SES 73 Deployteq 1
cleverreach.atlassian.netAmazon SES 59
unbxddev.atlassian.netAmazon SES 59
growens.atlassian.netAmazon SES 51
vercom.atlassian.netAmazon SES 34
accentgr.atlassian.netBloomreach 18 Amazon SES 15
tinuiti.atlassian.netAmazon SES 32
makingsense.atlassian.netAmazon SES 29
gymbeam.atlassian.netAmazon SES 27
po.atlassian.netAmazon SES 26
financialtimes.atlassian.netAmazon SES 24 Keap 1
windsorfashions.atlassian.netAmazon SES 23
benchmark.atlassian.netAmazon SES 21
sparkfly-dev.atlassian.netAmazon SES 20
rebrandly.atlassian.netAmazon SES 18
id.atlassian.comAmazon SES 17
donorschoose.atlassian.netAmazon SES 17
ecomz.atlassian.netAmazon SES 11
nanit.atlassian.netAmazon SES 9
tutorful.atlassian.netAmazon SES 9
adwise.atlassian.netAmazon SES 8
su-jsm.atlassian.netAmazon SES 8
restauranclub.atlassian.netAmazon SES 7
harlemnext.atlassian.netAmazon SES 7
id.atlassian.netAmazon SES 5
am.atlassian.comAmazon SES 4
iterable.atlassian.netAmazon SES 4
omnisend.atlassian.netAmazon SES 3
embluemail.atlassian.netAmazon SES 3
trr-prod.atlassian.netAmazon SES 3
dartagnan.atlassian.netAmazon SES 2
communicatorcorp.atlassian.netAmazon SES 2
kahnit.atlassian.netAmazon SES 2
neharathourami.atlassian.netAmazon SES 2
huzaifasworkspace-37981332.atlassian.netAmazon SES 2
pragmawoo.atlassian.netAmazon SES 1
percona.atlassian.netAmazon SES 1
bloomreach.atlassian.netBloomreach 1
happyhorizon.atlassian.netAmazon SES 1
webpower.atlassian.netAmazon SES 1
halonsecurity.atlassian.netAmazon SES 1
stibodx.atlassian.netAmazon SES 1
zenpatient.atlassian.netAmazon SES 1