Why did I get a "Sending domain is no longer verified" email?

This article explains the “Sending domain acme.com is no longer verified” email, what it means for your sending, and how to restore the domain.

Symptoms

• The workspace owner received an email with the subject Sending domain acme.com is no longer verified. It lists the status of SPF, DKIM and the return path.
• The domain shows Not verified in Email API›Domains.
• New API requests from that domain fail with 422 Domain not verified (From/Sender domain is not valid or not verified), and SMTP replies 530 From/Sender domain is not verified for this workspace.

Cause

Emailit re-checks the DNS records of every domain once a day. If any of the three required records fails, the domain loses its verified status and the owner is emailed once. Typical reasons:

• Someone edited DNS. A record was deleted during a cleanup, a website migration or a change of DNS provider.
• Nameservers changed. The domain moved to a new DNS host, such as Cloudflare, and the Emailit records weren’t copied over.
• Records were overwritten. A tool or hosting panel replaced the zone, or a new MX record was added at emailit.acme.com.
• The domain expired or its registration lapsed.

Emails that were already queued or scheduled before the check still go out. Only new sends are refused. If the DNS lookups merely time out, Emailit leaves the domain as it is.

Fix

1. See what failed. Open the domain in Email API›Domains. The records marked Missing or Invalid show the error Emailit found.

2. Restore the records. Re-create them at your current DNS provider with the values shown on the domain page. Run dig NS acme.com +short first to confirm which provider is authoritative. See DNS records.

3. Check DNS. Select Check DNS. As soon as SPF, DKIM and the return path are OK, the domain is verified again and sending resumes. You don’t need to wait for the daily check.

4. Resend failed mail. Requests rejected while the domain was unverified weren’t sent and weren’t charged. Send them again from your application.

5. Protect the records. Note the three Emailit records in your DNS documentation, or use the Cloudflare integration with an API token so you can Sync records after changes.

On Pay as you go, a domain that Emailit already approved after the new-domain review doesn’t need another review. Fixing DNS is enough. For more help with records, see Why are my DNS records not verifying? and Domain verification.

Still stuck?

Contact support or ask in Discord with the domain name and the record statuses from the email.