<ul><li>When accessing an SSL site via IP instead of domain, it may return a different certificate, often the default one.</li><li>The issue occurs because the TLS handshake happens before the server receives the HTTP request, and IP addresses are not supported in Server Name Indication (SNI).</li><li>When no SNI is provided, SafeLine falls back to the default virtual host certificate or its built-in 404 fallback site certificate.</li><li>To avoid this problem, always access SSL sites via the domain name and understand the role of SNI in certificate negotiation to prevent SSL errors.</li></ul>

Why Does My SSL Site Return the Wrong Certificate When Accessed via IP?

Discover more