Opens in a new tab

atlassian-… and s1: Atlassian’s DKIM keys

Atlassian signs Jira and Confluence email for your domain with two CNAMEs at names like atlassian-8d2d08, one active and one for rotation. Older setups used s1 and s2 CNAMEs to atlassian.net — the same names as SendGrid’s, which is a known clash.

WhoseAtlassian (Jira, Confluence) — work software
Selectoratlassian-<code> — or s1, s2
Published asTwo CNAMEs at atlassian-<code> names; older setups have s1 and s2 CNAMEs to atlassian.net
RotationTwo records so a key can rotate
Where to find itadmin.atlassian.com → Settings → Emails → Email domains → See DNS records
Can it go?Once no Atlassian product sends from the domain; Atlassian checks the records every 24 hours and emails admins when they change.

Is Atlassian (Jira, Confluence)’s key on your domain?

Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Atlassian (Jira, Confluence)’s key under s1 and s2, check it, and name every other key the domain publishes.

The records

The current shape, and the older one:

atlassian-8d2d08._domainkey.example.com  CNAME  <value Atlassian shows>
s1._domainkey.example.com  CNAME  s1._domainkey.atlassian.net

How it works

The older s1 and s2 point on into SendGrid, so a domain that also sends through its own SendGrid account cannot have both — Atlassian tracks this clash as JRACLOUD-74314.

Common mistakes

  • GoDaddy doubling the domain in the name.

Sources

Checked on 27 September 2026 against these official sources:

Know when a DKIM key disappears

Point your DMARC reports at us and we monitor the keys your mail is signed with — and email you when one stops answering, before receivers start failing your mail. Free for your first domain.

Create a free account