Deep SSL/TLS Vulnerability Test
This report provides a deep analysis of the SSL/TLS configuration of api.web-live.link. It checks for protocol support, cipher strength, and known vulnerabilities.
Scan Results
Testing all IP addresses (port 443): 3.138.62.161 3.132.151.150 3.141.57.222 ----------------------------------------------------- Start 2026-06-09 03:41:29 -->> 3.138.62.161:443 (api.web-live.link) <<-- Further IP addresses: 3.141.57.222 3.132.151.150 2600:1f16:114c:3501:8d29:b22e:8efc:ab1 2600:1f16:114c:3500:3f5e:27bb:5250:97dd 2600:1f16:114c:3502:d30:1b92:a642:3613 rDNS (3.138.62.161): ec2-3-138-62-161.us-east-2.compute.amazonaws.com. Service detected: HTTP Testing for server implementation bugs No bugs found. Testing HTTP header response @ "/" HTTP Status Code 400 Bad Request (Hint: better try another URL) HTTP clock skew 0 sec from localtime Strict Transport Security not offered Public Key Pinning -- Server banner nginx/1.30.0 Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 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) make sure you don't use this certificate elsewhere with SSLv2 enabled services, see https://search.censys.io/search?resource=hosts&virtual_hosts=INCLUDE&q=345160CCCCECCD4597C19B8B9DFE333BEB529D2E09B1F282D335FAE93612EF77 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-RSA-AES128-SHA ECDHE-RSA-AES256-SHA AES128-SHA 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) - CAMELLIA or ECDHE_RSA GCM ciphers found RC4 (CVE-2013-2566, CVE-2015-2808) no RC4 ciphers detected (OK) Done 2026-06-09 03:42:12 [ 52s] -->> 3.138.62.161:443 (api.web-live.link) <<-- ----------------------------------------------------- Start 2026-06-09 03:42:12 -->> 3.132.151.150:443 (api.web-live.link) <<-- Further IP addresses: 3.141.57.222 3.138.62.161 2600:1f16:114c:3501:8d29:b22e:8efc:ab1 2600:1f16:114c:3500:3f5e:27bb:5250:97dd 2600:1f16:114c:3502:d30:1b92:a642:3613 rDNS (3.132.151.150): ec2-3-132-151-150.us-east-2.compute.amazonaws.com. Service detected: HTTP Testing for server implementation bugs No bugs found. Testing HTTP header response @ "/" HTTP Status Code 400 Bad Request (Hint: better try another URL) HTTP clock skew 0 sec from localtime Strict Transport Security not offered Public Key Pinning -- Server banner nginx/1.30.0 Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 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) make sure you don't use this certificate elsewhere with SSLv2 enabled services, see https://search.censys.io/search?resource=hosts&virtual_hosts=INCLUDE&q=345160CCCCECCD4597C19B8B9DFE333BEB529D2E09B1F282D335FAE93612EF77 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-RSA-AES128-SHA ECDHE-RSA-AES256-SHA AES128-SHA 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) - CAMELLIA or ECDHE_RSA GCM ciphers found RC4 (CVE-2013-2566, CVE-2015-2808) no RC4 ciphers detected (OK) Done 2026-06-09 03:42:59 [ 99s] -->> 3.132.151.150:443 (api.web-live.link) <<-- ----------------------------------------------------- Start 2026-06-09 03:43:00 -->> 3.141.57.222:443 (api.web-live.link) <<-- Further IP addresses: 3.138.62.161 3.132.151.150 2600:1f16:114c:3501:8d29:b22e:8efc:ab1 2600:1f16:114c:3500:3f5e:27bb:5250:97dd 2600:1f16:114c:3502:d30:1b92:a642:3613 rDNS (3.141.57.222): ec2-3-141-57-222.us-east-2.compute.amazonaws.com. Service detected: HTTP Testing for server implementation bugs No bugs found. Testing HTTP header response @ "/" HTTP Status Code 400 Bad Request (Hint: better try another URL) HTTP clock skew 0 sec from localtime Strict Transport Security not offered Public Key Pinning -- Server banner nginx/1.30.0 Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 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) make sure you don't use this certificate elsewhere with SSLv2 enabled services, see https://search.censys.io/search?resource=hosts&virtual_hosts=INCLUDE&q=345160CCCCECCD4597C19B8B9DFE333BEB529D2E09B1F282D335FAE93612EF77 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-RSA-AES128-SHA ECDHE-RSA-AES256-SHA AES128-SHA 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) - CAMELLIA or ECDHE_RSA GCM ciphers found RC4 (CVE-2013-2566, CVE-2015-2808) no RC4 ciphers detected (OK) Done 2026-06-09 03:43:58 [ 158s] -->> 3.141.57.222:443 (api.web-live.link) <<-- ----------------------------------------------------- Done testing now all IP addresses (on port 443): 3.138.62.161 3.132.151.150 3.141.57.222
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.