Android throws this (java.security.cert.CertPathValidatorException) when the server certificate is signed by a CA missing from the Android system truststore. Three causes: (1) self-signed or private CA, (2) incomplete chain — server doesn't send the intermediate, (3) old Android < 7 doesn't know newer CAs (Let's Encrypt R3 since 2021). Fix: install the full chain on the server or add the CA to network_security_config.xml.
Below: details, example, related, FAQ.
<!-- res/xml/network_security_config.xml -->
<network-security-config>
<base-config>
<trust-anchors>
<certificates src="system"/>
<certificates src="@raw/my_ca"/> <!-- res/raw/my_ca.pem -->
</trust-anchors>
</base-config>
</network-security-config>
<!-- AndroidManifest.xml -->
<application android:networkSecurityConfig="@xml/network_security_config" ...>SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.
Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).
Full chain verification: from leaf certificate through intermediates to root CA.
Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.
Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.
SSL certificate monitoring
TLS config audit
HTTPS as ranking factor
customer trust
www and subdomains.Strict-Transport-Security header forces browsers to always use HTTPS.SSL certificate monitoring, check history and alerts 30 days before expiry.
Sign up freecurl -v https://host 2>&1 | grep -i "issuer\|depth\|ssl". Or enterno.io/ssl — shows intermediate + leaf.
ISRG Root X1 cross-signed via DST Root CA X3. Expired 30 Sep 2021, LE resumed cross-sign — works until 2025+.
network_security_config — per-app (API 24+). Device-wide — needs rooted device + push CA to /system/etc/security/cacerts/.