←Back to Guides
🔒Transport Security⏱️ 15 min read•Updated November 2026•✍️By Chris

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.

#TLS 1.3#HTTPS#Let’s Encrypt#ACME#mTLS#OpenSSL#HSTS#SSL

1. TLS 1.3 Anatomy & Deprecating Broken Protocols (TLS 1.0/1.1)

TLS 1.3 (RFC 8446) strips vulnerable RSA static key transport, CBC padding oracles, and extra round trips—completing key exchange via Ephemeral Elliptic Curve Diffie-Hellman (ECDHE) in a single round trip (1-RTT). Always disable TLS 1.0/1.1, enforce AEAD ciphers (TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256), and present fullchain.pem (leaf + intermediate) rather than leaf-only cert.pem.
Inspect Live Certificate Chain, TLS Version & ALPN via OpenSSL
openssl s_client -connect mayonlinetools.com:443 -servername mayonlinetools.com -tls1_3 -showcerts </dev/null | openssl x509 -noout -dates -subject -issuer

Verifies SNI hostname matching, exact TLS 1.3 negotiation, intermediate chain completeness, and expiry dates.

TLS ProtocolHandshake LatencyCipher ClassProduction StatusCopy
TLS 1.0 / 1.12-RTT legacyDeprecated RC4/CBC/SHA-1Disallowed (PCI-DSS / Browsers fail)
TLS 1.2 (Hardened)2-RTTECDHE + AES-GCM onlySupported fallback for older clients
TLS 1.3 (RFC 8446)1-RTT (0-RTT optional)Forward-secret AEAD onlyRecommended modern default (A+)

2. Let’s Encrypt ACME Automation: HTTP-01 vs Wildcard DNS-01 & CAA Records

Automated 90-day certificate rotation eliminates manual renewal failures. Use 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.
Verify ACME & CAA Domain Governance Before Issuance
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

Standard HTTPS authenticates only the server. Mutual TLS requires both server and client to swap and verify signed X.509 certificates during the TLS handshake—ideal for zero-trust microservice meshes, webhooks, and admin APIs where stolen bearer tokens alone should never grant access.
TLS ModeWho Presents X.509 CertPrimary DefenseCommon PitfallCopy
Standard HTTPSServer onlyServer identity + encrypted wireMissing intermediate chain breaks curl/Android
mTLS (Mutual)Both Server and ClientZero-trust service identityForgetting CRL/OCSP client revocation check

4. HSTS Headers & Preload Rollout Discipline

Sending 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.
👨‍💻
Authored & Reviewed by ChrisMayPixels • Netherlands

Independent software developer focused on client-side architectures, local-first computing, WebAssembly, and privacy-first web systems.

About MayOnlineTools→

🎓Explore More Guides

✨