www.urllo.com
The essential guide to SSL/TLS security & certificate automation ...
Excerpt
### Why does my certificate say "not trusted" even though it's valid? A certificate can show “not trusted” even when it’s valid because something in the trust chain, configuration or browser environment is incorrect. Here are the most common reasons: 1. **Missing intermediate certificates.** If the server isn’t sending the full certificate chain, browsers can’t verify the link between your certificate and the root authority. 2. **Wrong domain name (hostname mismatch).** The certificate must match the exact domain the user is visiting (including subdomains like … vs. non-www). 3. **Untrusted Certificate Authority (CA).** The certificate was issued by a CA that isn’t in the browser’s trusted root store, common with private, internal or self-signed certs. 4. **Outdated device or browser.** Older systems may not recognize newer root certificates, causing trust errors even for fully valid certs. 5. **Mixed HTTP/HTTPS resources.** If secure pages pull in insecure content or scripts, some browsers show warnings that resemble trust issues.
Related Pain Points
Mixed HTTP/HTTPS Content Causes Blocking and Security Issues
6Mixing HTTPS and HTTP protocols in the same page causes content blocking, performance degradation, and security vulnerabilities. Developers must maintain protocol consistency across all resources.
Certificate Chain Validation Issues Across Different SSL Stacks
6Cross-signing of CA certificates creates multiple possible trust chains. Different SSL stacks (Windows, OpenSSL) behave differently during verification, causing some platforms to fail validation while others succeed.
Domain Name Mismatch Between Certificate and Hostname
6SSL certificates fail to validate when the domain name in the certificate does not match the exact domain being visited, including subdomain variations (www vs. non-www). This hostname mismatch triggers trust errors for otherwise valid certificates.
Trust Store Mismatches Between System and Application Trust Roots
5The Root CA may be known on the system but not present in the specific application's trust store, causing certificate verification failures even though the CA is globally trusted.