According to Live Direct Marketing's daily Tranco top-1M scan (July 13, 2026), Atlassian (Jira/Confluence) is the SaaS sender for 1,824 domains — 0.30% of 617,702 SPF-publishing domains. Detection method: include: mechanisms in the SPF record.
Atlassian operates Jira and Confluence, widely-used platforms for project management, issue tracking, and team collaboration. Like most SaaS vendors, Atlassian sends transactional and notification emails on behalf of customer organisations — project updates, workflow alerts, release notifications — and authenticates these messages through SPF, DKIM, and DMARC mechanisms that customers configure in their own DNS records.
Atlassian's presence in email infrastructure is concentrated among smaller and mid-market organisations, particularly in the .com domain space, where it commonly appears in SPF records alongside Microsoft 365. For email senders and deliverability engineers, this footprint pattern reflects the adoption curve of both platforms as a specialist project-management layer on top of enterprise Microsoft environments. Understanding how Atlassian fits into multi-vendor email authorisation is essential when designing SPF records that stack multiple SaaS include mechanisms without exceeding DNS lookup constraints.
| Tranco rank band | Domains | Share of its base |
|---|---|---|
| Top 1,000 | 4 | 0.2% |
| Top 10,000 | 41 | 2.2% |
| Top 100,000 | 331 | 18.1% |
| Top 1,000,000 | 1,362 | 74.7% |
| Unranked | 86 | 4.7% |
| TLD | Domains | Share | |
|---|---|---|---|
| .com | 1,048 | 57.5% | |
| .org | 88 | 4.8% | |
| .de | 85 | 4.7% | |
| .net | 45 | 2.5% | |
| .io | 44 | 2.4% | |
| .com.au | 36 | 2.0% | |
| .nl | 28 | 1.5% | |
| .co.uk | 27 | 1.5% | |
| .edu | 22 | 1.2% | |
| .pl | 18 | 1.0% |
Cross-tabulated from the same daily snapshot — the other email services seen on the same 1,824 domains.
| Type | Service | Domains | Share of Atlassian (Jira/Confluence) users |
|---|---|---|---|
| Mailbox | Microsoft 365 | 801 | 43.9% |
| Mailbox | Google Workspace | 520 | 28.5% |
| Mailbox | Mimecast | 106 | 5.8% |
| Mailbox | Proofpoint | 85 | 4.7% |
| Mailbox | Unknown / Other | 64 | 3.5% |
| Mailbox | Self-Hosted | 64 | 3.5% |
Jira and Confluence instances configured to send email — notifications, workflow transitions, bulk updates — require an SPF include to authenticate those messages as authorised by the customer's domain rather than Atlassian's infrastructure alone. The include mechanism allows Atlassian to publish centralised IP ranges authorised for all customer instances, so individual organisations avoid hardcoding long lists of Atlassian servers into their SPF records. This design keeps SPF simpler when an organisation uses multiple SaaS vendors in parallel, though the cumulative length of several includes can press against SPF's practical DNS lookup limits if not carefully ordered or consolidated.
See the full Atlassian (Jira/Confluence) data page (KPI cards, trend, sample domains) →
Yes, if your Jira or Confluence instance is configured to send email notifications and you want those messages to authenticate properly as coming from your domain — omitting it risks deliverability issues or rejection as spoofed. Your Atlassian instance administrator can provide the exact SPF include string required for your subscription tier and cloud region.
1,824 domains in the Tranco top-1M use Atlassian (Jira/Confluence) as their SaaS sender as of July 13, 2026 (0.30% of SPF-publishing domains), according to Live Direct Marketing's daily DNS scan.
Atlassian (Jira/Confluence) accounts for 0.30% of SPF-publishing domains in the top 1M. Whether you should seed a test mailbox there depends on how much of your audience it represents — the co-usage table above shows the services it appears alongside most.
Atlassian (Jira/Confluence) has been stable — its share moved -0.01 pp over the last 30 days (as of July 13, 2026).
Atlassian (Jira/Confluence)'s largest TLD is .com (57.5% of its domains); it appears across 130 TLDs in total.