Skip to main content

Domain Validation

Authorizing attack simulations on domains you own

Updated over a month ago

Validating your domains is essential for allowing the Arsen platform to test email addresses from your organization and ensure their legitimacy.

1 – Objectives

  • Confirm ownership or administrative control over the domains used for your emails

  • Authorize Arsen to send tests from these domains without risk of blocking

  • Ensure that simulations and awareness campaigns are properly authenticated and delivered

2 – Prerequisites

  • Access your Arsen account

  • Ability to modify the DNS zone of the domain to validate (DNS provider access)

  • (If applicable) Ensure sending servers from your internal infrastructure are already authorized

3 – Validate your domains

3.1 – Access domain management

  • Click your company logo (top-right)

  • Click Domains in the dropdown menu

Navigation to the Domains section from the user menu or sidebar

3.2 – Add a new domain

  • Click + Add New Domain

Domains section showing the Add New Domain button

  • Enter the domain name

  • Click Add Domain

Add New Domain window with input field and Add Domain button

The domain will now appear in the list, pending validation.

Verify your domain page showing DNS instructions and TXT record

3.3 – Retrieve the TXT value to add to DNS

Copy the value displayed under Enter This Value
This value is required to authenticate domain ownership.

3.4 – Add the TXT record in your DNS zone

  • Log into your DNS provider (OVH, Cloudflare, Gandi, etc.)

  • Add a TXT record at the root of your domain (field @)

  • Paste the value provided by Arsen

  • Save your DNS changes

3.5 – Verify the domain validation

  • Click Check your DNS records

Verify your domain interface showing expected and detected TXT records

Three possible outcomes:

  • Validation successful
    The domain is authenticated and ready for use.

Verified domain status displayed in green

  • Validation failed
    The TXT record is incorrect or placed in the wrong location.

Display showing incorrect TXT record

Propagation in progress
Wait a few minutes and try again (varies based on DNS TTL).

3.6 – Use your validated domains

  • Add employees whose email addresses belong to the validated domain

  • Begin sending tests or simulations from this domain

4 – Key considerations & best practices

  • Always add the TXT record at the root of the domain, never under a subdomain
    ​

  • Ensure no extra spaces or characters are included in the TXT value
    ​

  • Allow time for DNS propagation (from several minutes to several hours)
    ​

  • Keep DNS access available while tests are being conducted in case adjustments are needed

Related Articles
Allow Phishing Simulations via Email Headers in Google Workspace
Create an Allow List for Arsen Domains in Google Workspace
Domain monitoring
Did this answer your question?