TLS/SSL Configuration
What is TLS/SSL Configuration?
Validates HTTPS enforcement, certificate validity, protocol versions, and cipher suite strength.
This vulnerability class falls under the Configuration & Deployment Management phase of the OWASP Testing Guide (WSTG-CONF). Security engineers prioritise configuration & deployment management checks early in an assessment because weaknesses here provide a foothold that amplifies the severity of vulnerabilities found in later phases.
Security Impact
Weak TLS allows traffic interception. This module detects expired certs, weak ciphers, and missing HTTPS redirects.
Left undetected, tls/ssl configuration issues can persist unnoticed for months. Continuous automated scanning ensures your team receives an alert the moment a regression or new exposure is introduced — long before an attacker discovers it through manual enumeration or automated offensive tooling.
How DygDog Detects It
DygDog audits server configuration, exposed file paths, HTTP methods, and deployment artefacts without sending malicious payloads, making the check safe to run continuously in production.
The TLS/SSL Configuration check is implemented as a passive scan module, meaning it never sends dangerous payloads or modifies application state. Scans complete in approximately 1.0 s and run continuously in the background so your security posture reflects the current state of your site — not a point-in-time snapshot.
Sample Finding
The following illustrates what a positive TLS/SSL Configuration detection looks like in practice.
Observed
TLSv1.0 and TLSv1.1 accepted by the server alongside TLSv1.3. Certificate expires in 6 days. HTTP requests receive a 200 response instead of redirecting to HTTPS.
Risk
TLS 1.0/1.1 are deprecated and susceptible to POODLE and BEAST attacks. An expiring certificate causes browser warnings that block users and destroy trust. Plaintext HTTP exposes session tokens to network observers.
Fix
Disable TLS 1.0/1.1 in your server config (`ssl_protocols TLSv1.2 TLSv1.3;`), enable certificate auto-renewal via Let's Encrypt or Certbot, and add a permanent 301 redirect from http:// to https://.
Remediation Approach
Harden server and framework defaults by disabling unused HTTP methods, removing version banners from response headers, and applying a principle-of-least-privilege to file permissions and deployment artefacts.
DygDog does not stop at detection. When a TLS/SSL Configuration finding is confirmed, the platform generates infrastructure-aware, copy-paste-ready remediation snippets using frontier AI models. Instead of generic advice you need to adapt, you receive code that targets your exact server, framework, and configuration.
OWASP References
This check maps to the following OWASP Testing Guide test cases:
- WSTG-CONF-09View OWASP WSTG →
Related Configuration & Deployment Management Checks
These checks belong to the same testing phase and are often assessed together:
HTTP Methods Testing
Tests for dangerous HTTP methods (TRACE, PUT, DELETE, OPTIONS) that may be unintentionally enabled.
Security Headers Analysis
Comprehensive check for HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy.
File Extension & MIME Handling
Tests how the server handles various file extensions and MIME types, looking for bypass opportunities.
Backup & Unreferenced File Discovery
Probes for common backup files (.bak, .old, .sql), editor artifacts (.swp, ~), and unreferenced pages.
Detect TLS/SSL Configuration on Your Site
DygDog runs continuous passive scans across 74 vulnerability checks — including TLS/SSL Configuration — and notifies you the moment an issue is detected. Start a free scan in under 60 seconds, no installation required.
Start Free Scan