Deep SSL/TLS Vulnerability Test
This report provides a deep analysis of the SSL/TLS configuration of alb-external-470721412.us-east-1.elb.amazonaws.com. It checks for protocol support, cipher strength, and known vulnerabilities.
Scan Results
Testing all IP addresses (port 443): 98.94.247.106 34.226.232.159 ----------------------------------------------------- Start 2026-03-29 14:06:48 -->> 98.94.247.106:443 (alb-external-470721412.us-east-1.elb.amazonaws.com) <<-- Further IP addresses: 34.226.232.159 rDNS (98.94.247.106): ec2-98-94-247-106.compute-1.amazonaws.com. Service detected: HTTP Testing for server implementation bugs No bugs found. Testing HTTP header response @ "/" HTTP Status Code 404 Not Found (Hint: supply a path which doesn't give a "404 Not Found") HTTP clock skew 0 sec from localtime Strict Transport Security not offered Public Key Pinning -- Server banner awselb/2.0 Application banner -- Cookie(s) (none issued at "/") -- HTTP status 404 signals you maybe missed the web application Security headers -- Reverse Proxy banner -- Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation not vulnerable (OK) CRIME, TLS (CVE-2012-4929) not vulnerable (OK) BREACH (CVE-2013-3587) no gzip/deflate/compress/br HTTP compression (OK) - only supplied "/" tested POODLE, SSL (CVE-2014-3566) not vulnerable (OK) TLS_FALLBACK_SCSV (RFC 7507) some unexpected "handshake failure" instead of "inappropriate fallback" SWEET32 (CVE-2016-2183, CVE-2016-6329) not vulnerable (OK) FREAK (CVE-2015-0204) not vulnerable (OK) DROWN (CVE-2016-0800, CVE-2016-0703) not vulnerable on this host and port (OK) no RSA certificate, thus certificate can't be used with SSLv2 elsewhere LOGJAM (CVE-2015-4000), experimental not vulnerable (OK): no DH EXPORT ciphers, no DH key detected with <= TLS 1.2 BEAST (CVE-2011-3389) TLS1: ECDHE-ECDSA-AES128-SHA ECDHE-ECDSA-AES256-SHA VULNERABLE -- but also supports higher protocols TLSv1.1 TLSv1.2 (likely mitigated) LUCKY13 (CVE-2013-0169), experimental potentially VULNERABLE, uses obsolete cipher block chaining ciphers with TLS, see server prefs. Winshock (CVE-2014-6321), experimental not vulnerable (OK) - doesn't seem to be IIS 8.x RC4 (CVE-2013-2566, CVE-2015-2808) no RC4 ciphers detected (OK) Done 2026-03-29 14:07:41 [ 63s] -->> 98.94.247.106:443 (alb-external-470721412.us-east-1.elb.amazonaws.com) <<-- ----------------------------------------------------- Start 2026-03-29 14:07:41 -->> 34.226.232.159:443 (alb-external-470721412.us-east-1.elb.amazonaws.com) <<-- Further IP addresses: 98.94.247.106 rDNS (34.226.232.159): ec2-34-226-232-159.compute-1.amazonaws.com. Service detected: HTTP Testing for server implementation bugs No bugs found. Testing HTTP header response @ "/" HTTP Status Code 404 Not Found (Hint: supply a path which doesn't give a "404 Not Found") HTTP clock skew 0 sec from localtime Strict Transport Security not offered Public Key Pinning -- Server banner awselb/2.0 Application banner -- Cookie(s) (none issued at "/") -- HTTP status 404 signals you maybe missed the web application Security headers -- Reverse Proxy banner -- Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation not vulnerable (OK) CRIME, TLS (CVE-2012-4929) not vulnerable (OK) BREACH (CVE-2013-3587) no gzip/deflate/compress/br HTTP compression (OK) - only supplied "/" tested POODLE, SSL (CVE-2014-3566) not vulnerable (OK) TLS_FALLBACK_SCSV (RFC 7507) some unexpected "handshake failure" instead of "inappropriate fallback" SWEET32 (CVE-2016-2183, CVE-2016-6329) not vulnerable (OK) FREAK (CVE-2015-0204) not vulnerable (OK) DROWN (CVE-2016-0800, CVE-2016-0703) not vulnerable on this host and port (OK) no RSA certificate, thus certificate can't be used with SSLv2 elsewhere LOGJAM (CVE-2015-4000), experimental not vulnerable (OK): no DH EXPORT ciphers, no DH key detected with <= TLS 1.2 BEAST (CVE-2011-3389) TLS1: ECDHE-ECDSA-AES128-SHA ECDHE-ECDSA-AES256-SHA VULNERABLE -- but also supports higher protocols TLSv1.1 TLSv1.2 (likely mitigated) LUCKY13 (CVE-2013-0169), experimental potentially VULNERABLE, uses obsolete cipher block chaining ciphers with TLS, see server prefs. Winshock (CVE-2014-6321), experimental not vulnerable (OK) - doesn't seem to be IIS 8.x RC4 (CVE-2013-2566, CVE-2015-2808) no RC4 ciphers detected (OK) Done 2026-03-29 14:08:37 [ 119s] -->> 34.226.232.159:443 (alb-external-470721412.us-east-1.elb.amazonaws.com) <<-- ----------------------------------------------------- Done testing now all IP addresses (on port 443): 98.94.247.106 34.226.232.159
About this Scan
This scan uses testssl.sh to check for:
- Protocols: SSLv2, SSLv3, TLS 1.0, TLS 1.1, TLS 1.2, TLS 1.3
- Vulnerabilities: Heartbleed, POODLE, FREAK, Logjam, DROWN, etc.
- Cipher Suites: Weak ciphers, perfect forward secrecy (PFS) support.