I'm sorry to hear you're experiencing problems with your domain verification. I took a look at your domain and the Name Server record does not point to Route 53. This will mean that any record added in Route 53 is not resolved.
Please correct your NS record to point to Route 53 and restart the domain verification from the AWS SES console.
Thank you for the reply. My NS record includes 4 AWS DNS servers, is there another way I should point it to Route53? Thank you.
The problem of the incorrect NS records is with your domain registrar. I see that is also Route 53, so you can take those 4 domains from the NS record in the HostedZone and update the Name servers for your domain.
Thank you. I added the NS record entries to the domain and was successful after that.
Possible to Send Email as verified email identity vs. from verified domain?asked a year ago
Amazon SES Identity Management verification issueAccepted Answerasked 3 years ago
Pending verification workmail/ses route53asked 2 years ago
SES sent email lands in spam after activating Custom MAIL FROM domain and WorkMailasked 8 months ago
Verifying domain _amazonses. "Pending SES domain ownership verification"asked 4 years ago
SES and Workmail continues to say 'Pending Verification' of my domainasked 3 years ago
Workmail domain verification Route53 failedasked 10 months ago
aws ses receipt rules for routing email to an existing email addressasked 8 months ago
Can I use SES and WorkMail on the same domain?Accepted Answerasked 2 years ago
Do You Have to Add New MX or TXT Records to a Domain using SES?asked 3 years ago