SES domain identity stuck "Unverified" despite correct DNS (Easy DKIM)

When a domain identity remains unverified in Amazon SES despite correct DNS records being in place for over 72 hours, there are a few potential causes to investigate:

First, double-check that your CNAME records use the exact correct names. Some DNS providers, including Namecheap, automatically append the domain name to DNS records you create. For example, if you enter a record name like 'example._domainkey.thekitchencycle.com', your DNS provider might append '.thekitchencycle.com' to the end, resulting in 'example._domainkey.thekitchencycle.com.thekitchencycle.com'. This would cause verification to fail even though the records appear correct when you query them directly. Check your DNS provider's documentation or interface to see if you need to enter just the subdomain portion (like 'example._domainkey') rather than the full hostname.

Second, while you've verified the records resolve correctly from multiple public DNS servers, Amazon SES may be querying different DNS servers or encountering intermittent DNS propagation issues. In rare cases, it can take longer than 72 hours for DNS records to become fully visible to SES's verification systems.

If you've confirmed the record names are correct and accounted for any automatic domain appending by your DNS provider, you may want to try removing and re-adding the domain identity in SES to trigger a fresh verification attempt. Alternatively, consider temporarily using a DNS provider like Route 53, which is known to work reliably with SES verification.

For additional assistance with this specific verification issue, you can open a support case through the AWS Support Center at https://console.aws.amazon.com/support/ where the support team can investigate the specific DNS queries SES is making for your domain.
Sources
Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service
Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service

Ruled out the "doubled domain suffix" hypothesis: I confirmed via nslookup that the correctly-named record (iqrckio...domainkey.thekitchencycle.com) resolves correctly, while the "doubled" form (...thekitchencycle.com.thekitchencycle.com) returns NXDOMAIN — so Namecheap did not append the domain twice. Still stuck at "Unverified" past 72 hours with confirmed-correct DNS.

Hello.

Is it possible to share the specific contents of the DNS records?
When registering DNS records, please use a short TTL (Time To Live).
A long TTL may cause verification to take a long time.

Also, try deleting the record and then reconfiguring Easy DKIM in Amazon SES.
I've seen users resolve this issue using this method in the past.