TLS 1.3, Let’s Encrypt (ACME), mTLS & Certificate Chain Troubleshooting Runbook
Eliminate broken HTTPS chains and expiry outages: master the TLS 1.3 1-RTT handshake, fullchain intermediate bundling, Certbot ACME HTTP-01 vs DNS-01 challenges, strict HSTS, and mutual TLS (mTLS) service authentication.
1. TLS 1.3 Anatomy & Deprecating Broken Protocols (TLS 1.0/1.1)
TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256), and present fullchain.pem (leaf + intermediate) rather than leaf-only cert.pem.openssl s_client -connect mayonlinetools.com:443 -servername mayonlinetools.com -tls1_3 -showcerts </dev/null | openssl x509 -noout -dates -subject -issuerVerifies SNI hostname matching, exact TLS 1.3 negotiation, intermediate chain completeness, and expiry dates.
| TLS Protocol | Handshake Latency | Cipher Class | Production Status | Copy |
|---|---|---|---|---|
| TLS 1.0 / 1.1 | 2-RTT legacy | Deprecated RC4/CBC/SHA-1 | Disallowed (PCI-DSS / Browsers fail) | |
| TLS 1.2 (Hardened) | 2-RTT | ECDHE + AES-GCM only | Supported fallback for older clients | |
| TLS 1.3 (RFC 8446) | 1-RTT (0-RTT optional) | Forward-secret AEAD only | Recommended modern default (A+) |
2. Let’s Encrypt ACME Automation: HTTP-01 vs Wildcard DNS-01 & CAA Records
HTTP-01 (serving a token under /.well-known/acme-challenge/ on port 80) for single internet-facing hosts, and DNS-01 (writing a _acme-challenge TXT record via DNS API) for wildcard certificates (`*.example.com`) or private internal intranets. Publish a DNS CAA record so unauthorized Certificate Authorities cannot issue certs for your domain.dig +short CAA example.com
# Expected: 0 issue "letsencrypt.org"Restricts certificate issuance exclusively to your approved Certificate Authority.
3. Mutual TLS (mTLS): Zero-Trust Client Certificate Verification
| TLS Mode | Who Presents X.509 Cert | Primary Defense | Common Pitfall | Copy |
|---|---|---|---|---|
| Standard HTTPS | Server only | Server identity + encrypted wire | Missing intermediate chain breaks curl/Android | |
| mTLS (Mutual) | Both Server and Client | Zero-trust service identity | Forgetting CRL/OCSP client revocation check |
4. HSTS Headers & Preload Rollout Discipline
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload instructs browsers never to attempt plaintext HTTP connections again. Test first with max-age=300 across every subdomain before committing a 1-year TTL or submitting to the global HSTS preload list, because internal HTTP-only tools under *.yourdomain will immediately become unreachable.Related Free Online Tools
Put these techniques into practice immediately with our privacy-first browser utilities:
Inspect CAA, AAAA, TXT _acme-challenge, and DNSSEC records privately via encrypted DoH.
Generate SHA-256/384/512 integrity attributes alongside HTTPS transport security.
Generate and inspect cryptographic RSA/SPKI keys offline inside Web Crypto memory.
Independent software developer focused on client-side architectures, local-first computing, WebAssembly, and privacy-first web systems.