All the sudden my site show insecure connection even though all SSLs in place?

Hi @HOA ELECTION EXPERTS LLC
It sounds like your site is suddenly showing “Not secure” even though you believe all your SSL certs are in place. Here are the most common causes and things to check in your Azure App Service:

Verify Certificate Binding

• In the Azure portal, go to your Web App > TLS/SSL settings > Bindings Make sure you have a binding for every custom hostname (e.g., root domain and www subdomain).
• Ensure the certificate’s thumbprint and the hostname listed match exactly.

Confirm the Certificate Covers Your Domain

• Check the Subject Name or SAN entries in the cert. If you’re browsing www.yourdomain.com but the certificate only covers yourdomain.com, you’ll see a mismatch.
• Use a wildcard cert or separate certs for each hostname if needed.

Check for an Expired or Mis-synchronized Certificate

• Has the cert just expired? Look at the expiration date in App Service Certificates or Key Vault.
• If you’re using Key Vault-backed certs, verify that your App Service access policies allow the latest version and then force a manual sync: – Azure portal > App Service Certificates > select your cert > Rekey and Sync > Sync.

Confirm DNS Is Pointing to the Right App

• Use a tool like digwebinterface.com to compare the IP address returned for your custom domain vs. yourapp.azurewebsites.net.
• If they differ, your DNS may be pointing to an App Service instance that doesn’t have your cert bound.

Check Certificate Chain and Browser Error Details

• Visit the site in incognito or another device to rule out caching.
• Click the padlock (or warning icon) to view the browser’s error code (e.g., ERR_CERT_COMMON_NAME_INVALID, ERR_CERT_DATE_INVALID, untrusted issuer). That clue tells you if it’s a name-mismatch, expired cert, or missing intermediate.
• If the intermediate CA is missing, re-export your PFX including the full chain and re-upload.

Consider a Front-End Service or CDN in Front of Your App

• If you have Azure Front Door, Application Gateway, or another CDN/WAF, make sure that service is presenting the correct cert. The App Service cert binding only affects connections directly to the App Service endpoint.

Minimum TLS Version & Cipher Suites

• Under App Service > TLS/SSL settings, confirm your Minimum TLS version is appropriate (e.g., 1.2 or 1.3).
• In multitenant App Service you can’t tweak individual ciphers—consider ASE or Application Gateway if you need more TLS customization.
  https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-custom-domain-issues-azure-app-service
  https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-domain-and-tls-ssl-certificates
  Let me know if you have any further assistances needed.