TLS, HTTPS, and What a Check Can Tell You
HTTPS is HTTP over TLS. A connection check can tell you something about a particular hostname now, but it cannot certify an entire website as safe.
What TLS protects—and what it does not
TLS protects data in transit through confidentiality and integrity checks, and authenticates the server during a verified connection. HTTPS applies TLS to HTTP traffic. It does not fix application vulnerabilities, phishing, malicious content, or stolen accounts.
A valid certificate and a sound overall TLS configuration are different questions. A certificate verifies an identity and trust chain for the hostname; it does not by itself show which protocol versions or cipher options a server supports.
Read a version result in its proper scope
Utilook tries actual TLS handshakes for TLS 1.3 and TLS 1.2 separately, using the server-side TLS client and a validated public hostname on port 443. The result shows which of these two versions that client could negotiate; it is not an exhaustive scan of all versions or cipher suites.
The displayed preferred protocol, cipher, and certificate expiry come from a successful verified connection. If certificate-chain or hostname verification fails, the checker reports a certificate error rather than treating the two versions as unsupported.
Why one successful check is not a security guarantee
The checker accepts a hostname, not a URL or an IP literal. It resolves public addresses and attempts connections to port 443 with a four-second timeout per attempt. It does not inspect URL paths, page content, HTTP security headers, all server configurations, or the site's application code.
Results reflect the reachable addresses and server configuration at the time of the test. Another client or a later deployment may observe something different; review certificate errors separately from timeouts and connection failures.
Where the input goes
The hostname is sent from your browser to the Utilook backend, which resolves it and opens outbound TLS connections to public addresses. The checker does not store the submitted hostname or result in its database; successful checks contribute only to aggregate tool-use counts.