Verify a Sending Domain

Verify a sending domain

A verified domain lets SendNeo sign and deliver messages for your brand. Open Domains, choose Add domain, and enter the domain or sending subdomain you plan to use.

SendNeo displays three DKIM CNAME records, a custom MAIL FROM subdomain, and a recommended DMARC TXT record. Copy the values exactly. DNS providers sometimes add the zone name automatically, so check the final hostname after saving.

Why use a subdomain?

A sending subdomain such as mail.example.com keeps mail-specific authentication and reputation separate from the website at example.com. It also makes it easier to identify mail records when several services share the parent domain. You can still use a friendly address such as news@mail.example.com.

The records SendNeo gives you

DKIM CNAME records

Publish all three CNAME records. They point to SendNeo's DKIM targets and allow receiving providers to verify the signature on each message. Do not proxy DKIM CNAME records through a DNS provider's HTTP proxy.

Custom MAIL FROM

SendNeo uses a subdomain such as bounce.example.com for the envelope sender. Add:

If the dashboard gives a different exact host, use the dashboard value. These records are for the custom MAIL FROM subdomain, not for your visible From address.

DMARC recommendation

Publish the suggested TXT record at _dmarc.example.com, for example:

v=DMARC1; p=none; rua=mailto:dmarc@example.com

Use the mailbox you control for aggregate reports. DMARC aligns the visible From domain with SPF and/or DKIM and gives receiving providers a policy for messages that fail alignment.

Provider steps

Cloudflare

1. Open the zone and choose DNS > Records.
2. Add each CNAME, MX, and TXT record from SendNeo.
3. Leave mail records as DNS-only; do not enable the orange cloud on DKIM CNAME records.
4. Cloudflare may show the zone name separately from the host. Confirm that the resulting record ends in the intended domain only once.

GoDaddy

1. Open DNS Management for the domain.
2. Choose Add and select the record type shown by SendNeo.
3. In the Host field, enter the relative name (for example, _dmarc or bounce) if GoDaddy appends the domain automatically.
4. Set the MX priority to 10 and leave TXT values unquoted unless the provider adds quotes for you.

Namecheap

1. Open Advanced DNS and choose Add New Record.
2. Use CNAME Record, MXE/MX Record, or TXT Record as appropriate.
3. Enter only the host prefix when Namecheap supplies the domain automatically.
4. Save all records, then wait for propagation before verification.

DNS caches can make a correct change appear old for a while. SendNeo's Verify action checks the public DNS view; it does not require you to keep the dashboard open.

Verify and troubleshoot

Return to Domains, select the domain, and choose Verify. If verification fails:

• compare every character of each CNAME target with the dashboard;
• remove duplicate DKIM or DMARC records at the same hostname;
• make sure a proxy is disabled for DKIM CNAME records;
• check that the MAIL FROM MX points to the Amazon SES endpoint with priority 10;
• wait for DNS propagation and run verification again.

Do not create several competing SPF TXT records. If the parent domain already has SPF, merge the required mechanism into one valid SPF record according to your DNS provider's limits.

Roll out DMARC gradually

Start with p=none so you can observe reports while authenticating legitimate senders. After you have reviewed reports and confirmed that SendNeo and other authorized senders align, move to p=quarantine. When legitimate mail consistently passes and unauthorized sources are understood, move to p=reject.

Change one policy step at a time and keep a reporting address during the rollout. DMARC is a domain policy; it does not replace list permission, one-click unsubscribe, or good sending practice. See Deliverability for review mode and list hygiene.