Why domain verification comes early
Email campaigns perform better when mailbox providers can recognise and trust the sending identity. Domain verification is part of that trust. It proves ownership, supports signing, and helps protect the brand from weak sender configuration.
Step 1: Add the domain correctly
- Enter the root domain that appears after the @ sign in the sender email address.
- Use a domain that the business actually controls in DNS.
- Check spelling carefully before saving, because one wrong character can delay the full process.
Step 2: Copy each DNS record exactly
NexaMail shows the exact record type, host, and value required for verification. These details should be copied exactly into the DNS provider panel. Small formatting mistakes often keep the status stuck on pending.
| Check | Purpose | What to remember |
|---|---|---|
| Identity verification | Confirms control of the domain. | Usually the fastest way to prove ownership. |
| DKIM | Adds a trusted signature to outgoing messages. | Improves credibility with receiving servers. |
| SPF | Defines which servers are allowed to send for the domain. | There should only be one SPF TXT record for the domain. |
Step 3: Understand propagation and re-checking
DNS changes do not appear instantly everywhere. Some records verify within minutes, while others can take much longer. Re-checking is normal. A pending state immediately after saving DNS is not automatically a problem.
Important SPF ruleIf the domain already has an SPF record, the new sending mechanism usually needs to be merged into that existing record instead of creating a second SPF entry.
What users learn from this step
- Why authentication is part of deliverability, not just technical setup.
- How to move between NexaMail and the DNS provider without losing accuracy.
- Why a fully verified identity should be in place before campaigns are created.