SSL/TLS (Secure Sockets Layer / Transport Layer Security) encrypts data between browsers and servers. Proper SSL/TLS configuration prevents eavesdropping, man-in-the-middle attacks, and content tampering. Our tests cover the full transport security chain: from certificate validity to browser enforcement policies. Test selection follows the OWASP TLS Cheat Sheet and relevant IETF standards.
TLS
HTTPS Available
+15 / -20HTTPS encrypts all traffic between the browser and your server using TLS. Without HTTPS, all data — passwords, form submissions, cookies — is sent in plain text and can be intercepted by anyone on the network. HTTPS is the foundation of web security and a ranking factor for search engines.
Reference: RFC 8446 (TLS 1.3), RFC 9325
301
HTTP→HTTPS Redirect
+10 / -10When users type a URL without "https://", browsers default to HTTP. A 301 redirect from HTTP to HTTPS ensures every visitor gets the encrypted version automatically. Without this redirect, users who reach your site over HTTP stay on an unencrypted connection.
Reference: RFC 7231 §6.4.2
STS
HSTS Configuration
+15 / -15HTTP Strict Transport Security (HSTS) instructs browsers to only connect via HTTPS for a specified duration. This prevents SSL stripping attacks where an attacker intercepts the initial HTTP request. Best practice: max-age=31536000 (1 year), includeSubDomains, and preload for browser preload list inclusion.
Reference: RFC 6797 · hstspreload.org
EXP
Certificate Expiry
+15 / -15Expired certificates cause browsers to display security warnings that drive visitors away. Certificates have a limited validity period (typically 90 days for Let's Encrypt, 1 year for commercial CAs). Auto-renewal via ACME protocol eliminates the risk of accidental expiration.
Reference: RFC 8555 (ACME)
CT
Certificate Transparency
+10 / -10Certificate Transparency (CT) logs are public, append-only records of every certificate issued by participating CAs. Domain owners can monitor these logs to detect unauthorized or misissued certificates. Chrome requires all certificates to be logged to CT since April 2018.
Reference: RFC 6962 · certificate.transparency.dev
CA
Certificate Issuer
+10 / -5Certificates must be issued by a Certificate Authority (CA) trusted by browsers and operating systems. Self-signed certificates or certificates from unknown CAs will trigger browser warnings. Well-known CAs include Let's Encrypt, DigiCert, Sectigo, and GlobalSign.
Reference: Mozilla CA Certificate Policy
DA
DANE/TLSA Records
+10 / 0DANE (DNS-based Authentication of Named Entities) uses TLSA records in DNS to specify which TLS certificate a domain should present. This provides an alternative trust path independent of the CA system. DANE requires DNSSEC and is primarily used in mail server security (MTA-STS/DANE). No penalty for missing it.
Reference: RFC 6698, RFC 7671
DG
HTTPS Downgrade Protection
+10 / -15An HTTPS response that redirects to HTTP downgrades the user from an encrypted to an unencrypted connection. This can happen due to misconfigured redirects or mixed-content issues. HTTPS should never redirect to HTTP — it defeats the purpose of encryption and exposes users to interception.
Reference: RFC 9325 §3.1