Encryption Test — SSL/TLS Verification

doc

Check the encryption level of your connection. Verify SSL/TLS certificates, cipher suites, and HTTPS security.

Encryption scrambles data so that only parties holding the right key can read it, but it protects a specific layer and a specific moment. Understanding it means separating what encryption covers, the bytes on the wire or at rest, from what it does not: who the parties are, what metadata says, and what the receiving service retains on its own servers. A padlock in the address bar is not a verdict that the destination is trustworthy.

Symmetric and asymmetric keys split the work

Modern encryption uses two mechanisms together. Symmetric encryption uses one shared key to both lock and unlock data; it is fast and suited to bulk traffic. Asymmetric encryption uses a key pair, one half public and one half private; it solves the harder problem of agreeing on a shared secret over a channel that may be observed.

The TLS handshake shows the division in practice. The client and server do not encrypt a long conversation with asymmetric math; they use asymmetric operations to verify the server and negotiate a temporary symmetric key, then switch that fast cipher for the actual page traffic. Mixing the two keeps the protocol efficient while keeping key agreement secure.

What the TLS handshake actually does

  1. Certificate verification. The server presents a certificate binding its identity to a public key. The client checks that the certificate chains to a trusted issuer, matches the host name visited, and has not expired or been revoked.
  2. Key agreement. The client and server run a key exchange that produces a shared session secret without transmitting the secret itself over the connection.
  3. Forward secrecy. When the exchange uses ephemeral keys, each session negotiates fresh material. A compromise of a long-term server key later cannot decrypt older recorded sessions.
  4. Protected exchange. After verification and agreement, records are encrypted and integrity-checked so tampering on the wire is detected.

The handshake proves the server controls the presented key for that name. It does not prove the organization behind the name is honest, accurate or safe to deal with.

What encryption protects and what it leaves open

ConceptProtectsDoes not protect
TLS on the connectionPage content and credentials from observers on the local network and transit pathWhat the destination server does with the data after it decrypts it; the domain lookup; the connection metadata
HTTPS certificateThat you reached the host named in the certificate through the verified chainThat the site owner is trustworthy, lawful or free of malicious content
Encrypted storageData at rest from someone reading the raw disks or drivesData after the authorized system unlocks it; access through a valid account or running service
VPN encryptionTraffic between your device and the tunnel exit from the local network and direct path observersTraffic between the exit and the final destination; the VPN provider's own visibility and logs
End-to-end encryptionMessage content between the two endpoints, including from the relay service holding the ciphertextWho messages whom, when, and how often; endpoint devices and accounts themselves

Reading an encryption result correctly

A TLS check typically reports the certificate, the issuer, the protocol version, the negotiated cipher suite and the validity dates. Read these as separate facts. A modern protocol and strong cipher say the channel was negotiated securely; they say nothing about whether the site handles your data responsibly. A certificate that matches the host and chains to a trusted issuer confirms identity for that domain; a certificate warning means the channel cannot be verified, which ranges from a local configuration problem to an intercepted connection.

Check the certificate details in the browser's connection information or with a header inspection tool: subject name, issuer, validity period and whether the chain resolves. Expired, name-mismatched or self-signed certificates break the verification step, and you should not assume the traffic is safe to proceed past the warning without understanding why it appeared.

Common misreads

  • "The padlock means the website is safe." It means the connection to that domain was encrypted and verified. Malicious and impersonating sites can run HTTPS as well.
  • "Encrypted storage means no one can read my files." Someone with access to the unlocked system, a valid login, or the running decrypted service sees plaintext as normal.
  • "End-to-end encryption hides everything." It protects message content. Contacts, timestamps, device state and account metadata remain visible to the endpoints and often to the service.
  • "A VPN encrypts my whole online life." It encrypts the segment to its exit. From the exit onward, protection depends on the destination's own TLS and the provider's practices.

Reasonable steps

  1. Force HTTPS where available. Prefer HTTPS versions of sites and treat plain HTTP logins and payments as unprotected.
  2. Inspect the certificate when something feels off. Name mismatch, odd issuer or sudden warnings deserve checking before you enter credentials.
  3. Know the boundary of your VPN. Ask what traffic the tunnel carries, what the provider logs, and what happens after the exit.
  4. Separate channel security from destination trust. Encryption answers who can read this on the path; it does not answer whether you should trust this service.

Frequently asked questions

Does HTTPS hide the domain I visit?

The page content is encrypted, but the domain may still be visible in the DNS lookup and in the outer connection to the site. Encryption does not cover that metadata on its own.

What is forward secrecy and does my connection have it?

Forward secrecy means session keys are freshly negotiated and not derivable from a long-term server key. A modern TLS check can show whether the exchange uses ephemeral key agreement; sessions without it remain decryptable if the server key is later exposed.

If a site uses strong encryption, can I enter my password safely?

The channel protects the password from transit observers. Whether it is safe to share still depends on the site's reputation, its account practices and whether the connection genuinely belongs to the intended service.