Deep SSL/TLS Vulnerability Test
This report provides a deep analysis of the SSL/TLS configuration of im-ws.tiktok.com. It checks for protocol support, cipher strength, and known vulnerabilities.
Scan Results
Testing all IP addresses (port 443): 23.33.85.205 23.33.85.201 23.33.85.213 23.33.85.208 23.33.85.217 23.33.85.214 23.33.85.206 23.33.85.215 23.33.85.210 ----------------------------------------------------- Start 2026-04-26 11:04:47 -->> 23.33.85.205:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.210 23.33.85.201 23.33.85.213 23.33.85.208 23.33.85.217 23.33.85.214 23.33.85.206 23.33.85.215 rDNS (23.33.85.205): a23-33-85-205.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: 599,2.17.209.7 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-7.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation VULNERABLE (NOT ok), DoS threat (10 attempts) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:05:35 [ 58s] -->> 23.33.85.205:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Start 2026-04-26 11:05:35 -->> 23.33.85.201:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.210 23.33.85.205 23.33.85.213 23.33.85.208 23.33.85.217 23.33.85.214 23.33.85.206 23.33.85.215 rDNS (23.33.85.201): a23-33-85-201.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 -1 sec from localtime IPv4 address in header X-Origin-Response-Time: 600,2.17.209.21 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-21.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation not vulnerable (OK) -- mitigated (disconnect after 4/10 attempts) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:06:22 [ 105s] -->> 23.33.85.201:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Start 2026-04-26 11:06:22 -->> 23.33.85.213:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.210 23.33.85.205 23.33.85.201 23.33.85.208 23.33.85.217 23.33.85.214 23.33.85.206 23.33.85.215 rDNS (23.33.85.213): a23-33-85-213.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: 625,2.17.209.26 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-26.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:07:12 [ 155s] -->> 23.33.85.213:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Start 2026-04-26 11:07:13 -->> 23.33.85.208:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.210 23.33.85.205 23.33.85.201 23.33.85.213 23.33.85.217 23.33.85.214 23.33.85.206 23.33.85.215 rDNS (23.33.85.208): a23-33-85-208.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: 602,2.17.209.27 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-27.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:07:59 [ 202s] -->> 23.33.85.208:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Start 2026-04-26 11:07:59 -->> 23.33.85.217:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.210 23.33.85.205 23.33.85.201 23.33.85.213 23.33.85.208 23.33.85.214 23.33.85.206 23.33.85.215 rDNS (23.33.85.217): a23-33-85-217.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: 599,2.17.209.15 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-15.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation not vulnerable (OK) -- mitigated (disconnect after 4/10 attempts) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:08:51 [ 254s] -->> 23.33.85.217:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Start 2026-04-26 11:08:51 -->> 23.33.85.214:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.210 23.33.85.205 23.33.85.201 23.33.85.213 23.33.85.208 23.33.85.217 23.33.85.206 23.33.85.215 rDNS (23.33.85.214): a23-33-85-214.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: 601,2.17.209.20 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-20.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation VULNERABLE (NOT ok), DoS threat (10 attempts) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:09:47 [ 310s] -->> 23.33.85.214:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Start 2026-04-26 11:09:47 -->> 23.33.85.206:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.210 23.33.85.205 23.33.85.201 23.33.85.213 23.33.85.208 23.33.85.217 23.33.85.214 23.33.85.215 rDNS (23.33.85.206): a23-33-85-206.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: 600,2.17.209.13 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-13.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation VULNERABLE (NOT ok), DoS threat (10 attempts) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:10:48 [ 371s] -->> 23.33.85.206:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Start 2026-04-26 11:10:48 -->> 23.33.85.215:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.210 23.33.85.205 23.33.85.201 23.33.85.213 23.33.85.208 23.33.85.217 23.33.85.214 23.33.85.206 rDNS (23.33.85.215): a23-33-85-215.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: 624,2.17.209.13 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-13.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation not vulnerable (OK) -- mitigated (disconnect after 4/10 attempts) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:11:41 [ 424s] -->> 23.33.85.215:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Start 2026-04-26 11:11:41 -->> 23.33.85.210:443 (im-ws.tiktok.com) <<-- Further IP addresses: 23.33.85.205 23.33.85.201 23.33.85.213 23.33.85.208 23.33.85.217 23.33.85.214 23.33.85.206 23.33.85.215 rDNS (23.33.85.210): a23-33-85-210.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: 597,2.17.209.12 (check if it's your IP address or e.g. a cluster IP) Strict Transport Security 365 days=31536000 s, includeSubDomains Public Key Pinning -- Server banner (no "Server" line in header, interesting!) Application banner -- Cookie(s) (none issued at "/") -- HTTP status 400 signals you maybe missed the web application Security headers X-Content-Type-Options: nosniff Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Reverse Proxy banner X-Cache: TCP_MISS from a2-17-209-12.deploy.akamaitechnologies.com (AkamaiGHost/22.5.0-aaef44c942a33f2d231f7120051a5b09) (-) Testing vulnerabilities Secure Renegotiation (RFC 5746) supported (OK) Secure Client-Initiated Renegotiation not vulnerable (OK) -- mitigated (disconnect after 2/10 attempts) 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) 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=E3EACF5BF9D91AEF39A8BB70827620BC1B7D54B03DC28CA1F517052ADAEBEF0D 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-04-26 11:12:36 [ 479s] -->> 23.33.85.210:443 (im-ws.tiktok.com) <<-- ----------------------------------------------------- Done testing now all IP addresses (on port 443): 23.33.85.205 23.33.85.201 23.33.85.213 23.33.85.208 23.33.85.217 23.33.85.214 23.33.85.206 23.33.85.215 23.33.85.210
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.