Hi @innovationchef ,
Welcome to the forums! It’s possible that the SSL error is caused by a mismatch between the SSL certificate on your custom domain and the domain name that users are trying to access.
Checking on the DNS configuration, I see that www.siterecon.ai subdomain looks properly configured:
www.siterecon.ai is an alias for cute-capybara-bb5bc2.netlify.app.
cute-capybara-bb5bc2.netlify.app has address 18.104.22.168
cute-capybara-bb5bc2.netlify.app has address 22.214.171.124
cute-capybara-bb5bc2.netlify.app has IPv6 address 2600:1f18:2489:8201::c8
cute-capybara-bb5bc2.netlify.app has IPv6 address 2600:1f18:2489:8200::c8
However, for the apex domain, siterecon.ai, I’m showing that a AAAA Record (IPv6) is configured:
siterecon.ai has address 126.96.36.199
siterecon.ai has IPv6 address 2a02:4780:11:778:0:19d6:bcdd:1
siterecon.ai mail is handled by 1 aspmx.l.google.com.
siterecon.ai mail is handled by 10 alt4.aspmx.l.google.com.
siterecon.ai mail is handled by 10 alt3.aspmx.l.google.com.
siterecon.ai mail is handled by 5 alt2.aspmx.l.google.com.
siterecon.ai mail is handled by 5 alt1.aspmx.l.google.com.
We don’t support Pv6 when using our load balancer IP address. Please remove the IPv6 record.
Also, it looks like you’ve reached the rate limit of failed attempts at Let’s Encrypt (to learn more about LE rate limits, please see Failed Validation Limit - Let's Encrypt) . After you fix the AAAA Record (IPv6) you’ll need to wait for the rate limit hold to lift before Let’s Encrypt can renew the cert, or you can upload a custom certificate.