Atlassian Cloud - Domain Verify

Do you have questions or need help? Feel free to contact us.

Arrange a free consultation

Why should I verify a domain?

When you verify accounts, Atlassian informs users with the appropriate domain that your organization manages the accounts when they access their profile.

You must verify your organization's domain to prove that all user accounts with that domain belong to you. The organization domain is what follows the @ sign in the email addresses of the user accounts.

When you verify a domain for your organization, they do two things: 1.) You confirm that the company domain belongs to you, 2.) You claim the user accounts with that domain.

Verifying a domain has two benefits:

  • More control over the Atlassian accounts for the enterprise domain: These accounts become "managed accounts". This means that you can edit, delete, or deactivate these accounts.
  • The ability to apply security policies to your managed accounts: You then have the option to enforce two-factor verification or establish SAML-based single-sign-on so that your identity service policies apply to all Atlassian accounts. You can do both via Atlassian Access.

Verified domains in your organization   Confirm the ownership of a domain   Verification via HTTPS   Verification via DNS

Verify domains in your organization

Example: Your organization is called MeineFirma GmbH and has the domains and After verifying both domains and their accounts, you can go to the "Managed accounts" page under "Atlassian organization" and edit the user details.

Atlassian Access allows you to enforce security policies for your users' managed accounts.

You can still grant access to a product to users with other domains, but since these are not managed accounts, you cannot apply the above security policies in this case.

Confirm ownership of a domain

You can verify the ownership of your company domain (or multiple domains) in two ways:

  • HTTPS - uploading an HTML file to the root directory of the website with your domain.
  • DNS-TXT - copying a TXT record into your Domain Name System (DNS).

Verification via HTTPS

HTTPS is mandatory for hosting a HTML file and a valid SSL certificate from a certificate authority is required. (Self-signed certificates do not work.) You can only check domains with a redirect to a WWW domain. (Example: If your domain is, domains can be successfully verified for and, for example, but not for other redirects.)

After successful verification, Atlassian periodically checks the verification file for security reasons. If the file is ever deleted, Atlassian can no longer verify that the domain belongs to you; then that domain loses its verification status and the corresponding security mechanisms for that domain (SAML SSO is also no longer available).

To verify your domain via HTTPS:

  1. In your organization's account at, click Directory > Domains (or Settings > Domains in some instances).
  2. Under the HTTPS tab, download the atlassian-domain-verification.html file.
  3. Upload the HTML file to the root directory of your domain's web server.
  4. Return to the Domains page in Atlassian Administration and click Verify domain.
  5. HTTPS must be selected as the verification method. Enter the domain you want to verify in the domain field and click Verify domain.

When the system finds the HTML file on your web server, the domain is verified and the Claim accounts screen opens.

Verification via HTTPS does not work?

For security reasons, the domain verification process requires HTTPS for hosting the HTML file. The domain requires a valid SSL certificate from a certificate authority.

Only forwarding to a domain with WWW prefix is possible. For example, you can successfully verify only the domains and/or You can verify a domain that redirects to a second domain.

Verification via DNS

After successful verification, Atlassian periodically checks the DNS host against the TXT record. If it is deleted or updated with incorrect information, you receive an email from Atlassian announcing that you must update or correct the TXT record within a specified period of time.

If you fail to do so, the domain loses verification status and the relevant security mechanisms for that domain become inactive (including SAML SSO).

How to verify your domain via DNS:

  1. In your organization's account at, click Directory > Domains (or Settings > Domains in some instances).
  2. In the DNS tab, copy the TXT record to the clipboard.
  3. Go to your DNS host and access the configuration page to add a new record.
  4. Select the option to add a new record and paste the TXT record you copied earlier in the "Value" field (or "Answer" or "Description" in some systems).
  5. The DNS record should have approximately these fields:
    - Record type: Paste TXT
    - Name/Host/Alias: Keep default (@ or empty)
    - Time to live (TTL): enter "86400
  6. Save the record.
  7. Return to Atlassian administration and click "Verify domain".
  8. "TXT Record" must be selected as the method, then enter the domain in the appropriate field and click "Verify domain" again.

Depending on your DNS host, it may take up to 72 hours for the domain to be verified and for the DNS changes to take effect. Then the domain remains at UNVERIFIED status in the domains table. After 72 hours have passed, click "Verify domain" next to the domain you want to verify.

More on this topic:

  • No labels

This content was last updated on 11/30/2022.

This content hasn't been updated in a while. That doesn't have to be a problem. Some of our pages live for years without becoming obsolete. Please click this link if you want us to update this page. Old content can be incorrect, misleading or outdated. Please get in contact with us via a form on this page, our live chat or via email with if you are in doubt, have a question, suggestion, or want changes from us.