CNAME is not propagating, yet ANAME is, Error 403 presented

[vaeziborna]

What is the name of the domain?

‘legalrescue.ai’

What is the error number?

403

What is the error message?

The request could not be satisfied. Bad request. We can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. Generated by cloudfront (CloudFront) Request ID: FAuFUl1KGq3PS0teWSA2N2BWg5E4n_gh0SUPxDc7OXX7FAiIcGNqJw==

What is the issue you’re encountering

CNAME is not propagating, yet ANAME is, Error 403 presented. I have AWS Amplify. I cannot find my CNAME records under whatsmydns.net

What feature, service or problem is this related to?

DNS records

[sjr]

@vaeziborna

CNAME is not propagating, yet ANAME is,

What is the CNAME? (Cloudflare doesn’t have ANAMEs, just flattens the CNAME at the apex).

Records for your domain and www are not proxied so if for those, any issue is at your AWS end.

You also have 2 SPF and 2 DMARC records when you must have only one of each, so you’ll need to fix that as well…
https://cf-staging.sjr.dev/tools/check?a00288d8b4e24b58bdb8ed29b5fe46a9#dns