SES DKIM verification stuck in pending despite correct DNS records

Based on the information provided, if your DKIM CNAME records are correctly configured and DNS propagation is complete, here are some additional troubleshooting steps to consider:

Wait for the Full Verification Period While you've waited 24 hours, DKIM verification can take up to 72 hours in rare cases for the DNS records to become fully visible to Amazon SES. I recommend waiting the full 72-hour period before taking further action.

Verify DNS Record Names Even though you've confirmed the records are configured, double-check that the CNAME record names are exactly correct. Some DNS providers, including GoDaddy, automatically append the domain name to records you create. For example, if you created a record with a name like example._domainkey.internetwale.com, GoDaddy might automatically add your domain to the end, resulting in example._domainkey.internetwale.com.internetwale.com, which would be incorrect.

To avoid this issue, you may need to enter only the subdomain portion (the part before your domain name) when creating the CNAME records in GoDaddy, rather than the full hostname. Check GoDaddy's documentation or support resources for how they handle CNAME record creation.

Regional Configuration Since you mentioned you're using the ap-south-1 region, ensure that you're checking the DKIM status in the correct region in the SES console, as DKIM must be configured separately for each AWS region.

If after 72 hours the verification is still pending and you've confirmed the DNS records are correctly formatted for GoDaddy's requirements, there may be a service-side issue that would require AWS Support assistance to investigate further.
Sources
Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service
Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service