When a DNS record doesn't verify
The three most common causes: a Cloudflare record that is proxied (orange cloud), a name with the domain typed twice, or a record that hasn't shown up yet. The Domain & Email tab shows each record's state and the reason it fails.
Open Domain & Email (Opens in the Mujaz app). Each DKIM row shows its state: “Found” means it is right, “Waiting” means Mujaz hasn't found it yet, and “Not right yet” means it exists but something is wrong, with the reason next to it.
The three DKIM records (CNAME)
- Cloudflare's orange cloud: each of the three records must be “DNS only” (grey cloud), not “Proxied” (orange). Proxied records never verify. Click the cloud until it turns grey, then save.
- Domain typed twice: GoDaddy, Namecheap and most hosts add your domain to the name automatically, so type only the part before it. For example, in the zone yoursite.com for newsletter.yoursite.com, type abc123._domainkey.newsletter. Pasting the full name makes it end in yoursite.com.yoursite.com. Cloudflare accepts the full name.
- A typo: use the “Copy” button next to each Name and Value instead of typing, and check the record type is CNAME.
The bounce address (MX and SPF)
- Both records go on bounce.domain, not on the domain itself. The typed-twice rule applies here too.
- The MX record points to feedback-smtp.us-east-1.amazonses.com with priority 10.
- Never add a second SPF record to your main domain; a domain can only have one. Your existing record stays as it is.
DMARC
If your domain already has a DMARC record, keep it and add nothing. If it has none, Mujaz shows a monitor-only record on _dmarc.domain: v=DMARC1; p=none;.
Waiting
Records can take a few minutes to show up, sometimes a few hours. After adding them, press “Check records”. Mujaz also re-checks by itself every 30 minutes for the first 72 hours.
Still Failed after 72 hours
- 1. Press “Remove” next to the domain.
- 2. Type the domain again and press “Register”.
- 3. Replace the records at your provider with the new ones. They have new tokens.
Errors when registering
- “Please enter a valid domain”: type only the domain, such as newsletter.yoursite.com, with no https:// and no /. Arabic-script domains are not supported.
- “This domain is already registered by another account.”: another Mujaz workspace has it. Contact support if the domain is yours.
- “This domain is reserved”: it is one of Mujaz's own domains.
- “Failed to register domain. Please try again later.”: try again, then contact support if it keeps happening.
Common questions
Does the subdomain need a website?
No. It needs no website, A record or hosting. Only the email records.
I already have an SPF record. Should I change it?
No. Keep it as it is. The SPF record Mujaz asks for goes on bounce.domain, which is a separate name.
Related articles
- Send from your own domain
Register a domain such as newsletter.yoursite.com under “Custom Domain”, add the three DKIM records at your DNS provider, then change “From Email” to an address on that domain. Available from the Growth plan.
- Meet Mujazly
Mujazly is the assistant inside Mujaz that answers questions about the platform and your account. It reads your numbers, your setup and the issue you have open, but it never sends, publishes or changes anything.
- My issues land in spam
The strongest step is sending from your own verified domain, then sending only to people who want your issues. Go through this checklist item by item.
- How to stay out of spam
Send only to people who asked for your newsletter, use full direct links, send to engaged readers, check the “Spam Score Checker” tips before sending, and send from your verified domain if you can. Mujaz handles the rest: an unsubscribe link in every email, no more mail to bounced or complaining addresses, and link checks before sending.