How do I set up Jira and Jira Service Management (Atlassian) so its email passes DMARC?
Publish the records Jira and Jira Service Management (Atlassian) shows in your account for your domain.
Last read from the sources at the foot of this page.
What does Jira and Jira Service Management (Atlassian) ask me to publish?
Emails that are sent out using a custom email address other than the atlassian.net domain from Jira cloud can be rejected by DMARC if without a domain-specific DKIM signature.
Jira and Jira Service Management (Atlassian) prints these values in its own documentation, the same for every customer.
Jira and Jira Service Management (Atlassian) makes the other values for your account, so we do not print them here.
include:_spf.atlassian.netWhere in Jira and Jira Service Management (Atlassian) are my values shown?
Go to Atlassian Administration . Select your organization if you have more than one. Select Oganization settings , then Emails . Select the Email domains tab. Select See DNS records for the domain you want to manage.
In Atlassian Administration, select your organization, then Organization settings, then Emails, then the Email domains tab, and choose See DNS records.
Copy each value from there exactly as shown, and add each record at your DNS host.
How do I add Jira and Jira Service Management (Atlassian) to the SPF record I already have?
SPF implementations MUST limit the total number of those terms to 10 during SPF evaluation, to avoid unreasonable load on the DNS. If this limit is exceeded, the implementation MUST return "permerror".
Add include:_spf.atlassian.net inside the one SPF record you have, before its last word, and keep every service already in it. Never add a second SPF record: two make the check fail for every message.
An SPF record may make at most 10 DNS lookups. Each include counts, and so do the includes inside it. Past 10, the check fails, so remove services you no longer use before you add a new one.
Will p=reject block Jira and Jira Service Management (Atlassian) email?
A message satisfies the DMARC checks if at least one of the supported authentication mechanisms: 1. produces a "pass" result, and 2. produces that result based on an identifier that is in alignment
Not once Jira and Jira Service Management (Atlassian) signs your email with your domain's DKIM key. DMARC passes when a message passes DKIM or SPF for your own domain, and the DKIM records Jira and Jira Service Management (Atlassian) gives you are on your domain.
Mail sent from a custom address can be rejected under DMARC if it has no DKIM signature for your own domain.
Atlassian says to keep a single SPF record on the domain and merge any others into it.
Before you raise your policy, read your DMARC reports and check that email from Jira and Jira Service Management (Atlassian) passes.
Where does this come from?
- Atlassian: Configure Jira Cloud to send emails on behalf of your domainsupport.atlassian.comRead 14 October 2026
- Atlassian: Troubleshoot unverified DNS checker for custom domain emailsupport.atlassian.comRead 14 October 2026
- Atlassian: What are the DNS records required for configuring DMARC?support.atlassian.comRead 14 October 2026
- Atlassian: Copy and add DNS records to your domain providersupport.atlassian.comRead 14 October 2026
- RFC 7208, Sender Policy Frameworkrfc-editor.orgRead 14 October 2026
- RFC 7489, DMARCrfc-editor.orgRead 14 October 2026
See what is open before anyone else does.
We read from outside, find each way in first, and show it with a check anyone can re-run. No access, nothing tested, no obligation.
- We read your firm from outside.
- You see what is open, with the proof for the lead finding.
- If it is worth it, you order.
What happens if you go ahead. More at getleaktrace.com/see-it-first/.
Read the transcript
- 72 hours. One domain. Nothing to install.
- Discover. Every way in, found from outside.
- Validate. Every finding, proven. Dated and checkable by anyone.
- Close. Forged email: one click per step, where we reach your DNS host and you approve it.
- You get the fix for the rest, step by step, and we re-check until it is closed.
- Monitor. On monitoring: email settings, look-alikes and new host names re-checked every hour. Alerts within the hour.
- Every paid assessment is human-verified before release.
- The AI defense layer for businesses. getleaktrace.com/see-it-first/