Deep SSL/TLS Vulnerability Test

This report provides a deep analysis of the SSL/TLS configuration of p1.ipstatp.com. It checks for protocol support, cipher strength, and known vulnerabilities.

Scan Results

Testing all IP addresses (port 443): 23.215.11.238 23.215.11.239
-----------------------------------------------------
 Start 2026-07-19 06:01:31        -->> 23.215.11.238:443 (p1.ipstatp.com) <<--

 Further IP addresses:   23.215.11.239 
 rDNS (23.215.11.238):   a23-215-11-238.deploy.static.akamaitechnologies.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
 IPv4 address in header       X-Origin-Response-Time: 27,23.209.83.95
                              (check if it's your IP address or e.g. a cluster IP)
                              X-Parent-Response-Time: 45,23.62.38.239
                              
 Strict Transport Security    not offered
 Public Key Pinning           --
 Server banner                TLB
 Application banner           X-Powered-By: ImageX
 Cookie(s)                    (none issued at "/") -- HTTP status 400 signals you maybe missed the web application
 Security headers             Access-Control-Allow-Origin: *
                              Cache-Control: max-age=30
 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)              No fallback possible (OK), no protocol below TLS 1.2 offered
 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)                     not vulnerable (OK), no SSL3 or TLS1
 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)
 RC4 (CVE-2013-2566, CVE-2015-2808)        no RC4 ciphers detected (OK)


 Done 2026-07-19 06:02:10 [  48s] -->> 23.215.11.238:443 (p1.ipstatp.com) <<--

-----------------------------------------------------
 Start 2026-07-19 06:02:10        -->> 23.215.11.239:443 (p1.ipstatp.com) <<--

 Further IP addresses:   23.215.11.238 
 rDNS (23.215.11.239):   a23-215-11-239.deploy.static.akamaitechnologies.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
 IPv4 address in header       X-Origin-Response-Time: 28,23.209.83.95
                              (check if it's your IP address or e.g. a cluster IP)
                              X-Parent-Response-Time: 39,23.62.38.238
                              
 Strict Transport Security    not offered
 Public Key Pinning           --
 Server banner                TLB
 Application banner           X-Powered-By: ImageX
 Cookie(s)                    (none issued at "/") -- HTTP status 400 signals you maybe missed the web application
 Security headers             Access-Control-Allow-Origin: *
                              Cache-Control: max-age=30
 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)              No fallback possible (OK), no protocol below TLS 1.2 offered
 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)                     not vulnerable (OK), no SSL3 or TLS1
 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)
 RC4 (CVE-2013-2566, CVE-2015-2808)        no RC4 ciphers detected (OK)


 Done 2026-07-19 06:02:52 [  90s] -->> 23.215.11.239:443 (p1.ipstatp.com) <<--

-----------------------------------------------------
Done testing now all IP addresses (on port 443): 23.215.11.238 23.215.11.239

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.

Run Another Scan Recent Scans