ERR_SSL_UNRECOGNIZED_NAME_ALERT — TLS alert 112: server has no cert for the requested SNI hostname. Causes: misconfigured nginx (missing server_name), Cloudflare Workers without a custom cert, legacy server with a single cert for all virtual hosts. Fix: add server block for requested hostname + valid cert.
Below: causes, fixes, FAQ.
server_name matches requested hostname exactlyopenssl s_client -connect ip:443 -servername hostnameSSL/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 freeYes. All modern browsers send SNI. Server without SNI support = legacy, fails with multiple HTTPS vhosts.
nginx: <code>server_name _;</code> matches undefined hosts. But cert must still match SNI (otherwise UNRECOGNIZED_NAME).
ECH (RFC 9460) encrypts SNI in TLS 1.3. Cloudflare supports 2023+, Chrome partial. Does not cause this error — server-side config is target.
<a href="/en/ssl">Enterno SSL checker</a> validates cert-vs-hostname. <a href="/en/monitors">Scheduled monitors</a> alert on mismatch.