If your sending domain stays pending or Mailcamp cannot verify one of the DNS records, the issue is usually caused by DNS propagation, an incorrect host value, a copied value that changed during paste, or an existing SPF/DMARC record that conflicts with the new record.
Use the domain details page in Sending domains as the source of truth. Copy the record type, host, and value exactly as Mailcamp shows them, then add or update those records in your DNS provider.
In Mailcamp, go to Sending domains.
Open the domain that is not verifying.
Review each DNS record and its current status.
Confirm that the domain name in Mailcamp matches the domain zone you are editing in your DNS provider.
After making DNS changes, return to Mailcamp and click Verify Now.
Check that the TXT record host matches the host shown in Mailcamp.
Check that the TXT value matches the verification value exactly.
Make sure the record was added to the correct domain, not a different domain or subdomain.
If your DNS provider automatically appends the domain name, enter only the host portion required by that provider.
Wait for DNS propagation, then click Verify Now again.
Confirm that the DKIM record type is TXT.
Copy the full DKIM host and value from Mailcamp without removing or changing characters.
Check that the DKIM value was not split, trimmed, or wrapped incorrectly by your DNS provider.
If your DNS provider adds the domain automatically, avoid entering the domain twice in the host field.
Do not reuse DKIM values from another domain or another email platform.
Check whether your domain already has an SPF TXT record.
A domain should normally have only one SPF record.
If an SPF record already exists, merge Mailcamp's SPF include/value into the existing SPF record instead of creating a second SPF record.
Make sure the SPF record starts with v=spf1 and has only one ending mechanism such as ~all or -all.
After updating SPF, wait for DNS propagation and verify again.
Check whether your domain already has a DMARC record at the _dmarc host.
A domain should normally have only one DMARC record.
If a DMARC record already exists, review it before replacing it because it may be used by other email systems.
Confirm that the DMARC value starts with v=DMARC1.
If you are unsure about an existing DMARC policy, keep the existing record and only update it when you understand the impact.
Duplicated host: some providers append the domain automatically, causing records like selector._domainkey.example.com.example.com.
Wrong DNS zone: the record was added to a different domain than the one added in Mailcamp.
Copied spaces or missing characters: long TXT values can be altered when pasted into DNS fields.
Multiple SPF records: having more than one SPF TXT record can cause SPF verification to fail.
Propagation delay: DNS records may take time before Mailcamp can read them.
Mailcamp marks the sending domain active when the required identity and DKIM checks pass.
SPF and DMARC are still important for deliverability, even if the main activation depends on the required verification checks.
After the domain is active, use an email address from that domain as your sender address.
If your sender address is still rejected, confirm that it uses the same verified domain.
Open the domain in Sending domains and compare every DNS record with your DNS provider.
Check that record type, host, and value match Mailcamp exactly.
Remove duplicate SPF or DMARC records if they conflict with the correct record.
Confirm that your DNS provider did not duplicate the domain name in the host field.
Wait for DNS propagation after every change.
Click Verify Now again after DNS changes have propagated.