Verify your domains

Prove which email domains Fallax may send simulations to.

Written By Ignace

Last updated 21 days ago

Fallax only sends simulations to addresses on domains you have proven you own. This keeps a workspace from ever targeting people outside your organisation. Manage this under Domains.

Three ways a domain gets verified

Badge	How it happens
Verified via SSO	A member of your workspace signs in with Google or Microsoft at that domain. This is live: if that member is removed, the proof goes with them.
Verified by DNS	You publish a TXT record that Fallax checks.
Verified via connector	The primary domain of the Microsoft 365 or Google Workspace tenant you connected.

Verify a domain by DNS

On Domains, click Add recipient domain.
Enter the domain, for example acme.com, and click Get TXT record.
At your DNS provider, add a TXT record named _fallax-verify.acme.com with the value Fallax shows you. It looks like fallax-domain-verification=….
Back in Fallax, click Re-check. The badge changes from Pending DNS to Verified by DNS.

DNS changes can take a few minutes to spread. If the check fails, wait a little and click Re-check again.

Good to know

Subdomains are included. Verifying acme.com also covers eu.acme.com.
Public mail domains cannot be verified. Gmail, Outlook.com and similar providers are never allowed.
Unverified people are skipped, not mailed. People at a domain you have not verified can still be listed, but at launch they are recorded as blocked and never receive anything.
Sending a test to yourself always works. Send test to me goes to your own address without a domain check.
Removing a domain stops all campaigns from sending to anyone at that domain.

No sending records needed

Fallax places simulations directly into mailboxes through your Google Workspace or Microsoft 365 connection. Nothing travels over the public internet, so there is no SPF, DKIM or DMARC to set up for simulations.

Was this helpful?

Still need help? Ask the team