SanchitGurukul Security Tool
Certificate Chain Validator
Inspect the complete TLS certificate chain, hostname coverage, validity, signatures, issuer relationships, and trust verification.
—
Not tested
| # | Role | Subject | Issuer | Valid until | Signature | Key | Status |
|---|
Recommendations
What this validator checks
Leaf certificate
Checks hostname coverage, expiry, key type and signature algorithm.
Intermediate chain
Checks issuer-to-subject relationships and whether intermediates are supplied in the expected order.
Trust verification
Uses the WordPress server's OpenSSL trust store to verify the presented certificate path.
Root handling
Roots are normally trusted locally and are often not sent by the server. Sending the root is unnecessary.
Example: Nginx full chain
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;Example: Apache full chain
SSLCertificateFile /etc/letsencrypt/live/example.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pemOpenSSL verification examples
openssl s_client -connect example.com:443 -servername example.com -showcerts
openssl verify -CAfile root.pem -untrusted intermediate.pem leaf.pemA successful result from this server does not guarantee every client trusts the same root store. Retest from browsers, mobile devices, APIs, load balancers, and external scanners.
Your feedback matters
Was this post helpful?
0
reactions