###########################################################
    testssl.sh       3.0rc5 from https://testssl.sh/dev/

      This program is free software. Distribution and
             modification under GPLv2 permitted.
      USAGE w/o ANY WARRANTY. USE IT AT YOUR OWN RISK!

       Please file bugs @ https://testssl.sh/bugs/

###########################################################

 Using "OpenSSL 1.0.2-chacha (1.0.2k-dev)" [~183 ciphers]
 on s1008:/virtual/sslcheck/testssl/testssl.sh-3.0rc5/bin/openssl.Linux.x86_64
 (built: "Jan 18 17:12:17 2019", platform: "linux-x86_64")


 Start 2019-09-19 00:15:29        --\>\> 210.197.64.173:443 (direct.tos.hirogin.co.jp) \<\<--

 rDNS (210.197.64.173):  210197064173.cidr.odn.ne.jp.
 Service detected:       HTTP


 Testing protocols via sockets except NPN+ALPN 

 SSLv2      not offered (OK)
 SSLv3      offered (NOT ok)
 TLS 1      offered
 TLS 1.1    offered
 TLS 1.2    offered (OK)
 TLS 1.3    not offered
 NPN/SPDY   not offered
 ALPN/HTTP2 not offered

 Testing cipher categories 

 NULL ciphers (no encryption)                  not offered (OK)
 Anonymous NULL Ciphers (no authentication)    not offered (OK)
 Export ciphers (w/o ADH+NULL)                 not offered (OK)
 LOW: 64 Bit + DES, RC[2,4] (w/o export)       offered (NOT ok)
 Triple DES Ciphers / IDEA                     offered (NOT ok)
 Average: SEED + 128+256 Bit CBC ciphers       offered
 Strong encryption (AEAD ciphers)              offered (OK)


 Testing robust (perfect) forward secrecy, (P)FS -- omitting Null Authentication/Encryption, 3DES, RC4 

 No ciphers supporting Forward Secrecy offered


 Testing server preferences 

 Has server cipher order?     yes (OK)
 Negotiated protocol          TLSv1.2
 Negotiated cipher            AES128-GCM-SHA256
 Cipher order
    SSLv3:     AES128-SHA AES256-SHA RC4-SHA RC4-MD5 DES-CBC3-SHA 
    TLSv1:     AES128-SHA AES256-SHA RC4-SHA RC4-MD5 DES-CBC3-SHA 
    TLSv1.1:   AES128-SHA AES256-SHA RC4-SHA RC4-MD5 DES-CBC3-SHA 
    TLSv1.2:   AES128-GCM-SHA256 AES256-GCM-SHA384 AES128-SHA256 AES256-SHA256
               AES128-SHA AES256-SHA DES-CBC3-SHA 


 Testing server defaults (Server Hello) 

 TLS extensions (standard)    "renegotiation info/#65281"
                              "max fragment length/#1"
 Session Ticket RFC 5077 hint no -- no lifetime advertised
 SSL Session ID support       yes
 Session Resumption           Tickets no, ID: yes
 TLS clock skew               Random values, no fingerprinting possible 
 Signature Algorithm          SHA256 with RSA
 Server key size              RSA 2048 bits
 Server key usage             Digital Signature, Key Encipherment
 Server extended key usage    TLS Web Server Authentication, TLS Web Client Authentication
 Serial / Fingerprints        06436012CB4E5031274A3CB8E1F73739 / SHA1 B29C5DECAF59700CE09BF280F0BD9C370EEA2066
                              SHA256 F68ED4406EB2D494DB5555CA4693B62253B8AF2935939A731B5EC1CB98B771A8
 Common Name (CN)             direct.tos.hirogin.co.jp
 subjectAltName (SAN)         direct.tos.hirogin.co.jp 
 Issuer                       DigiCert SHA2 Extended Validation Server CA (DigiCert Inc from US)
 Trust (hostname)             Ok via SAN and CN (same w/o SNI)
 Chain of trust               Ok   
 EV cert (experimental)       yes 
 \"eTLS\" (visibility info)     not present
 Certificate Validity (UTC)   156 \>= 60 days (2019-09-11 09:00 --> 2020-02-22 21:00)
 # of certificates provided   4
 Certificate Revocation List  http://crl3.digicert.com/sha2-ev-server-g2.crl
                              http://crl4.digicert.com/sha2-ev-server-g2.crl
 OCSP URI                     http://ocsp.digicert.com
 OCSP stapling                not offered
 OCSP must staple extension   --
 DNS CAA RR (experimental)    not offered
 Certificate Transparency     yes (certificate extension)


 Testing HTTP header response @ \"/\" 

 HTTP Status Code             302 Found, redirecting to "/index.html"
 HTTP clock skew              0 sec from localtime
 Strict Transport Security    not offered
 Public Key Pinning           --
 Server banner                (no "Server" line in header, interesting!)
 Application banner           --
 Cookie(s)                    (none issued at "/") -- maybe better try target URL of 30x
 Security headers             --
 Reverse Proxy banner         --


 Testing vulnerabilities 

 Heartbleed (CVE-2014-0160)                not vulnerable (OK), no heartbeat extension
 CCS (CVE-2014-0224)                       not vulnerable (OK)
 Ticketbleed (CVE-2016-9244), experiment.  not vulnerable (OK), no session ticket extension
 ROBOT                                     not vulnerable (OK)
 Secure Renegotiation (CVE-2009-3555)      not vulnerable (OK)
 Secure Client-Initiated Renegotiation     not vulnerable (OK)
 CRIME, TLS (CVE-2012-4929)                not vulnerable (OK)
 BREACH (CVE-2013-3587)                    no HTTP compression (OK)  - only supplied "/" tested
 POODLE, SSL (CVE-2014-3566)               VULNERABLE (NOT ok), uses SSLv3+CBC (check TLS_FALLBACK_SCSV mitigation below)
 TLS_FALLBACK_SCSV (RFC 7507)              Downgrade attack prevention NOT supported and vulnerable to POODLE SSL
 SWEET32 (CVE-2016-2183, CVE-2016-6329)    VULNERABLE, uses 64 bit block ciphers
 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
                                           https://censys.io/ipv4?q=F68ED4406EB2D494DB5555CA4693B62253B8AF2935939A731B5EC1CB98B771A8 could help you to find out
 LOGJAM (CVE-2015-4000), experimental      not vulnerable (OK): no DH EXPORT ciphers, no DH key detected with <= TLS 1.2
 BEAST (CVE-2011-3389)                     SSL3: AES128-SHA AES256-SHA
                                                 DES-CBC3-SHA 
                                           TLS1: AES128-SHA AES256-SHA
                                                 DES-CBC3-SHA 
                                           VULNERABLE -- but also supports higher protocols  TLSv1.1 TLSv1.2 (likely mitigated)
 LUCKY13 (CVE-2013-0169), experimental     potentially VULNERABLE, uses cipher block chaining (CBC) ciphers with TLS. Check patches
 RC4 (CVE-2013-2566, CVE-2015-2808)        VULNERABLE (NOT ok): RC4-SHA RC4-MD5


 Testing 370 ciphers via OpenSSL plus sockets against the server, ordered by encryption strength 

Hexcode  Cipher Suite Name (OpenSSL)       KeyExch.   Encryption  Bits     Cipher Suite Name (IANA/RFC)
-----------------------------------------------------------------------------------------------------------------------------
 x9d     AES256-GCM-SHA384                 RSA        AESGCM      256      TLS_RSA_WITH_AES_256_GCM_SHA384                    
 x3d     AES256-SHA256                     RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA256                    
 x35     AES256-SHA                        RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA                       
 x9c     AES128-GCM-SHA256                 RSA        AESGCM      128      TLS_RSA_WITH_AES_128_GCM_SHA256                    
 x3c     AES128-SHA256                     RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA256                    
 x2f     AES128-SHA                        RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA                       
 x05     RC4-SHA                           RSA        RC4         128      TLS_RSA_WITH_RC4_128_SHA                           
 x04     RC4-MD5                           RSA        RC4         128      TLS_RSA_WITH_RC4_128_MD5                           
 x0a     DES-CBC3-SHA                      RSA        3DES        168      TLS_RSA_WITH_3DES_EDE_CBC_SHA                      


 Running client simulations (HTTP) via sockets 

 Android 4.2.2                TLSv1.0 AES128-SHA, No FS
 Android 4.4.2                TLSv1.2 AES128-GCM-SHA256, No FS
 Android 5.0.0                TLSv1.2 AES128-GCM-SHA256, No FS
 Android 6.0                  TLSv1.2 AES128-GCM-SHA256, No FS
 Android 7.0                  TLSv1.2 AES128-GCM-SHA256, No FS
 Android 8.1 (native)         TLSv1.2 AES128-GCM-SHA256, No FS
 Android 9.0 (native)         TLSv1.2 AES128-GCM-SHA256, No FS
 Chrome 65 Win 7              TLSv1.2 AES128-GCM-SHA256, No FS
 Chrome 74 (Win 10)           TLSv1.2 AES128-GCM-SHA256, No FS
 Firefox 62 Win 7             TLSv1.2 AES128-SHA, No FS
 Firefox 66 (Win 8.1/10)      TLSv1.2 AES128-SHA, No FS
 IE 6 XP                      SSLv3   RC4-SHA, No FS
 IE 7 Vista                   TLSv1.0 AES128-SHA, No FS
 IE 8 Win 7                   TLSv1.0 AES128-SHA, No FS
 IE 8 XP                      TLSv1.0 RC4-SHA, No FS
 IE 11 Win 7                  TLSv1.2 AES128-GCM-SHA256, No FS
 IE 11 Win 8.1                TLSv1.2 AES128-GCM-SHA256, No FS
 IE 11 Win Phone 8.1          TLSv1.2 AES128-SHA256, No FS
 IE 11 Win 10                 TLSv1.2 AES128-GCM-SHA256, No FS
 Edge 15 Win 10               TLSv1.2 AES128-GCM-SHA256, No FS
 Edge 17 (Win 10)             TLSv1.2 AES128-GCM-SHA256, No FS
 Opera 60 (Win 10)            TLSv1.2 AES128-GCM-SHA256, No FS
 Safari 9 iOS 9               TLSv1.2 AES128-GCM-SHA256, No FS
 Safari 9 OS X 10.11          TLSv1.2 AES128-GCM-SHA256, No FS
 Safari 10 OS X 10.12         TLSv1.2 AES128-GCM-SHA256, No FS
 Apple ATS 9 iOS 9            No connection
 Tor 17.0.9 Win 7             TLSv1.0 AES128-SHA, No FS
 Java 6u45                    TLSv1.0 AES128-SHA, No FS
 Java 7u25                    TLSv1.0 AES128-SHA, No FS
 Java 8u161                   TLSv1.2 AES128-GCM-SHA256, No FS
 Java 9.0.4                   TLSv1.2 AES128-GCM-SHA256, No FS
 OpenSSL 1.0.1l               TLSv1.2 AES128-GCM-SHA256, No FS
 OpenSSL 1.0.2e               TLSv1.2 AES128-GCM-SHA256, No FS
 OpenSSL 1.1.0j (Debian)      TLSv1.2 AES128-GCM-SHA256, No FS
 OpenSSL 1.1.1b (Debian)      TLSv1.2 AES128-GCM-SHA256, No FS
 Thunderbird (60.6)           TLSv1.2 AES128-SHA, No FS

 Done 2019-09-19 00:16:38 [  72s] --\>\> 210.197.64.173:443 (direct.tos.hirogin.co.jp) \<\<--