SSL_ERROR_RX_UNKNOWN_RECORD_TYPE — Firefox received a TLS record with unknown content type (not 20, 21, 22, 23, 24). Frequent: MITM proxy inserting garbage, HTTP error page served on an HTTPS port (80 vs 443 mix-up), captive portal interception, or broken load balancer. Fix: confirm the server actually speaks TLS on 443.
Below: causes, fixes, FAQ.
openssl s_client -connect host:443 — should show TLS handshakecurl -vI https://host — HTTP/2 200 ok?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 freeFrom hotel/cafe Wi-Fi — yes. Try mobile hotspot. Error gone → captive portal. Usually a 302 redirect over HTTP.
Fatal config error. nginx serves plain HTTP on 443, client sends TLS, server answers plain HTTP → garbage bytes.
Cert pinning / HPKP (deprecated) / DANE. Or compare cert fingerprint: <code>openssl s_client | openssl x509 -fingerprint</code>.
ChangeCipherSpec(20), Alert(21), Handshake(22), ApplicationData(23), Heartbeat(24). Anything else is malformed.