Hardenize has joined Red Sift! Find out more in our blog post.
Web Security Overview
Error
HTTPS

Web sites need to use encryption to help their visitors know they're in the right place, as well as provide confidentiality and content integrity. Sites that don't support HTTPS may expose sensitive data and have their pages modified and subverted.
There are issues with this site's HTTPS configuration.

For all sites VERY IMPORTANT medium EFFORT
Supported and well configured
HTTPS Redirection

To deploy HTTPS properly, web sites must redirect all unsafe (plaintext) traffic to the encrypted variant. This approach ensures that no sensitive data is exposed and that further security technologies can be activated.

For all sites VERY IMPORTANT low EFFORT
Not supported
HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) is an HTTPS extension that instructs browsers to remember sites that use encryption and enforce strict security requirements. Without HSTS, active network attacks are easy to carry out.

For important sites VERY IMPORTANT medium EFFORT
Not supported
HSTS Preloaded

HSTS Preloading is informing browsers in advance about a site's use of HSTS, which means that strict security can be enforced even on the first visit. This approach provides best HTTPS security available today.

For important sites VERY IMPORTANT medium EFFORT
Not supported
Content Security Policy

Content Security Policy (CSP) is an additional security layer that enables web sites to control browser behavior, creating a safety net that can counter attacks such as cross-site scripting.

For important sites IMPORTANT high EFFORT
Email Security Overview
Unable to determine
No SMTP servers

This host doesn't specify any SMTP servers, which probably means that it doesn't receive email. We are unable to evaluate STARTTLS support, TLS, X.509, and DANE configuration.


DNS Zone

The global DNS infrastructure is organized as a series of hierarchical DNS zones. The root zone hosts a number of global and country TLDs, which in turn host further zones that are delegated to their customers. Each organization that controls a zone can delegate parts of its namespace to other zones. In this test we perform detailed inspection of a DNS zone, but only if the host being tested matches the zone.

Test not applicable
The host being tested doesn't match a DNS zone.

DNS Records

Correctly functioning name servers are necessary to hold and distribute information that's necessary for your domain name to operate correctly. Examples include converting names to IP addresses, determining where email should go, and so on. More recently, the DNS is being used to communicate email and other security policies.

Test failed
We've detected serious problems that require your immediate attention.

DNS Records

These are the results of individual DNS queries against your nameserver for common resource record types.

Name TTL Type Data
No valid resource records found

Backing DNS Queries

Below are all DNS queries we submitted while inspecting the resource records.

ID Server Question Name Type Status

DNSSEC

DNSSEC is an extension of the DNS protocol that provides cryptographic assurance of the authenticity and integrity of responses; it's intended as a defense against network attackers who are able to manipulate DNS to redirect their victims to servers of their choice. DNSSEC is controversial, with the industry split largely between those who think it's essential and those who believe that it's problematic and unnecessary.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Useful DNSSEC Tools

Certification Authority Authorization

CAA (RFC 8659) is a new standard that allows domain name owners to restrict which CAs are allowed to issue certificates for their domains. This can help to reduce the chance of misissuance, either accidentally or maliciously. In September 2017, CAA became mandatory for CAs to implement.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Analysis

Powerup!
There is no CAA policy on this domain
CAA policies can be used to restrict which CAs are allowed to issue certificates for a hostname. As such, CAA can be used to enforce an organization-wide policy and to prevent issuance of unauthorized certificates. The CA/Browser forum requires CAs to consult CAA configuration during certificate issuance from September 2017.

Email (SMTP)

An internet hostname can be served by zero or more mail servers, as specified by MX (mail exchange) DNS resource records. Each server can further resolve to multiple IP addresses, for example to handle IPv4 and IPv6 clients. Thus, in practice, hosts that wish to receive email reliably are supported by many endpoint.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Analysis

Notice
This host doesn't have any MX servers and doesn't receive its own email
This host doesn't specify any MX servers. According to the SMTP specification, in that case it should be assumed that the host itself is willing to receive email. We have checked and that's not the case. This host should probably deploy a NULL MX (RFC 7505) to indicate that email is not wanted, but in practice it doesn't matter a great deal.

Email TLS (SMTP)

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Email Certificates (SMTP)

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Email DANE (SMTP)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

SPF

Sender Policy Framework (SPF) is a protocol that allows domain name owners to control which internet hosts are allowed to send email on their behalf. This simple mechanism can be used to reduce the effect of email spoofing and cut down on spam.

Test passed
Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location kloon.work.gd
SPF version used by this policy.v spf1
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
dnsexit.com
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
-all

Analysis

Info
SPF policy found

Policy text: v=spf1 include:dnsexit.com -all

Location: kloon.work.gd

Good
SPF policy is valid
Good. Your SPF policy is syntactically valid.
Good
Policy uses default fail
Excellent. This policy fails hosts that are not allowed to send email for this domain name.
Good
Policy DNS lookups under limit
Good. Your policy stays under the limit of up to 10 DNS queries. The SPF specification Section 4.6.4. requires implementations to limit the total number of DNS queries. Policies that exceed the limit should not be used and may not work in practice.

Lookups: 1

SPF Policy Information Included policy

Host where this policy is located.Location dnsexit.com
SPF version used by this policy.v spf1
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
204.12.228.216/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
64.182.209.144/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
64.182.211.240/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
64.182.213.0/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
64.182.215.0/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
64.182.220.48/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
107.150.63.192/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
69.30.249.130/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
69.30.222.218/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
74.91.24.16/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
216.244.76.184/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
199.191.57.104/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
66.85.73.240/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
96.43.135.18/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
38.79.142.65/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
107.150.58.186/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
31.14.40.164
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
66.85.182.216/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
204.12.239.136/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
184.164.135.0/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.82.74
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.82.77
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
69.30.210.154/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.82.97
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.82.98
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
204.12.192.106/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.80.162
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
139.99.66.103
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
89.39.149.107
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.81.237
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
31.14.40.88
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.83.212
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.83.213
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.83.214
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
162.244.83.217
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
-all

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

MTA Strict Transport Security

SMTP Mail Transfer Agent Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections, and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

SMTP TLS Reporting

SMTP TLS Reporting (RFC 8460), or TLS-RPT for short, describes a reporting mechanism and format by which systems sending email can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations. TLS-RPT can be used with DANE or MTA-STS.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

HTTP (80)

To observe your HTTP implementation, we submit a request to the homepage of your site on port 80, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers.

Test passed
Everything seems to be well configured. Well done.

URL: http://kloon.work.gd/

1
http://kloon.work.gd/
HTTP/1.1 301 Moved Permanently
2
https://kloon.work.gd/
HTTP/1.1 200 OK

Analysis

Good
HTTP redirects to HTTPS
Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.kloon.work.gd/

1
http://www.kloon.work.gd/
HTTP/1.1 301 Moved Permanently
2
http://kloon.work.gd/
HTTP/1.1 301 Moved Permanently
3
https://kloon.work.gd/
HTTP/1.1 200 OK

Analysis

Good
HTTP redirects to HTTPS
Good. This plaintext HTTP server redirects to HTTPS.

HTTP (443)

To observe your HTTPS implementation, we submit a request to the homepage of your site on port 443, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers. We use the most recent set of headers returned from the tested hostname for further tests such as HSTS and HPKP.

Test passed
Everything seems to be well configured. Well done.

URL: https://kloon.work.gd/

1
https://kloon.work.gd/
HTTP/1.1 200 OK

URL: https://www.kloon.work.gd/

1
https://www.kloon.work.gd/
HTTP/1.1 301 Moved Permanently
2
https://kloon.work.gd/
HTTP/1.1 200 OK

WWW TLS

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed
Everything seems to be well configured. Well done.

TLS Configuration: kloon.work.gd (89.135.28.99)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Unknown preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Unknown preference
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Only strong suites supported
Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Good
All TLS connections with this server satisfy Chrome's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.kloon.work.gd (64.182.209.151)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
SSL v3
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Unknown preference
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Suite: TLS_RSA_WITH_IDEA_CBC_SHA
Suite ID: 0x7
Cipher name: IDEA
Cipher strength: 128 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_IDEA_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_RC4_128_SHA
Suite ID: 0xc011
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_RC4_128_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xc012
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 2048 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x67
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x6b
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_SEED_CBC_SHA
Suite ID: 0x96
Cipher name: SEED
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_SEED_CBC_SHA
 128 bits
Suite: TLS_DHE_RSA_WITH_SEED_CBC_SHA
Suite ID: 0x9a
Cipher name: SEED
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_SEED_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9e
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9f
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA384
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (DHE 2048 bits)
Shows cipher suite configuration for this protocol version.TLS v1.1
Unknown preference
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Suite: TLS_RSA_WITH_IDEA_CBC_SHA
Suite ID: 0x7
Cipher name: IDEA
Cipher strength: 128 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_IDEA_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_RC4_128_SHA
Suite ID: 0xc011
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_RC4_128_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xc012
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_SEED_CBC_SHA
Suite ID: 0x96
Cipher name: SEED
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_SEED_CBC_SHA
 128 bits
Suite: TLS_DHE_RSA_WITH_SEED_CBC_SHA
Suite ID: 0x9a
Cipher name: SEED
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_SEED_CBC_SHA
 128 bits (DHE 2048 bits)
Shows cipher suite configuration for this protocol version.TLS v1.0
Unknown preference
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Suite: TLS_RSA_WITH_IDEA_CBC_SHA
Suite ID: 0x7
Cipher name: IDEA
Cipher strength: 128 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_IDEA_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_RC4_128_SHA
Suite ID: 0xc011
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_RC4_128_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xc012
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_SEED_CBC_SHA
Suite ID: 0x96
Cipher name: SEED
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_SEED_CBC_SHA
 128 bits
Suite: TLS_DHE_RSA_WITH_SEED_CBC_SHA
Suite ID: 0x9a
Cipher name: SEED
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_SEED_CBC_SHA
 128 bits (DHE 2048 bits)
Shows cipher suite configuration for this protocol version.SSL v3
Unknown preference
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Suite: TLS_RSA_WITH_IDEA_CBC_SHA
Suite ID: 0x7
Cipher name: IDEA
Cipher strength: 128 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_IDEA_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_RC4_128_SHA
Suite ID: 0xc011
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_RC4_128_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xc012
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_SEED_CBC_SHA
Suite ID: 0x96
Cipher name: SEED
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_SEED_CBC_SHA
 128 bits
Suite: TLS_DHE_RSA_WITH_SEED_CBC_SHA
Suite ID: 0x9a
Cipher name: SEED
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_SEED_CBC_SHA
 128 bits (DHE 2048 bits)

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
Error
Insecure SSL 3.0 protocol supported
This server uses SSL 3.0, which is affected by the POODLE attack and should not be used with HTTP. Modern browsers no longer support this older protocol version.
Powerup!
TLS 1.3 not supported
TLS 1.3 is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance. This version of TLS should be the main protocol used with modern clients.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Warning
Insecure RC4 cipher supported
This server uses RC4, which is considered insecure Modern TLS clients no longer support this cipher and virtually all clients support one or more alternatives.

First encountered suite: TLS_RSA_WITH_RC4_128_SHA

Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Warning
Reconfigure server to use forward secrecy and authenticated encryption
Even though this server supports TLS 1.2, the cipher suite configuration is suboptimal. We recommend that you reconfigure the server so that the cipher suites providing forward secrecy (ECDHE or DHE in the name, in this order of preference) and authenticated encryption (GCM or CHACHA20 in the name) are at the top. The server must also be configured to select the best-available suite.
Powerup!
Server doesn't enforce cipher suite preferences
Servers that don't enforce cipher suite preferences select the first cipher suite they support from the list provided by clients. This approach doesn't guarantee that best-possible cipher suite is negotiated.
Error
Server is not compliant with Apple's CT requirements
Some or all connections to this server failed to satisfy Apple's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method. If certificate is the only SCT transport method shown, inspect the server's certificates for more information.

SCT transports: CERT

Notice
Server is not compliant with Chrome's CT requirements
Not all TLS connections with this server satisfy Chrome's CT requirements even. This is not necessarily a problem, as CT compliance is only required for certificates issued from May 2018.

SCT transports: CERT

Good
DHE server parameter not reused
This server does not reuse the private value used for the Diffie-Hellman key exchange.

WWW Certificates

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test failed
We've detected serious problems that require your immediate attention.

Certificate: kloon.work.gd

Leaf certificate kloon.work.gd
Issuer: Let's Encrypt
Not Before: 08 Feb 2025 15:08:15 UTC
Not After: 09 May 2025 15:08:14 UTC (expired 3 days 9 hours ago)
Key: EC 256 bits
Signature: SHA384withECDSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Error
Certificate expired
The certificate has expired and can no longer be used.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Notice
CT requirements not checked for expired certificates
Expired certificates usually refer to temporal CT logs that are retired once all certificates they hold expire. For this reason, we don't check CT compliance of expired certificates.
Error
Certificate not publicly trusted
This certificate is not trusted and can't be used on public web sites.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate
kloon.work.gd | 28dee1e
Not After: 09 May 2025 15:08:14 UTC (expired 3 days 9 hours ago)
Authentication: EC 256 bits (SHA384withECDSA)
 View details
Intermediate certificate
E6 | 76e9e28
Not After: 12 Mar 2027 23:59:59 UTC (expires in 1 year 9 months)
Authentication: EC 384 bits (SHA256withRSA)
 View details
Root certificate
ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 22 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details

Analysis

Good
Certificate chain is correct
Good. This chain contains all the right certificates and in the right order.

Certificate: www.kloon.work.gd

Leaf certificate audiofrahm.linkpc.net
Issuer: Sectigo
Not Before: 18 May 2022 00:00:00 UTC
Not After: 16 Aug 2022 23:59:59 UTC (expired 2 years 8 months ago)
Key: RSA 2048 bits
Signature: SHA384withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Error
Certificate doesn't match hostname
The provided certificate doesn't match the expected hostname.

Expected hostname: www.kloon.work.gd

Error
Certificate expired
The certificate has expired and can no longer be used.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Notice
CT requirements not checked for expired certificates
Expired certificates usually refer to temporal CT logs that are retired once all certificates they hold expire. For this reason, we don't check CT compliance of expired certificates.
Error
Certificate not publicly trusted
This certificate is not trusted and can't be used on public web sites.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate
audiofrahm.linkpc.net | 6e04fa4
Not After: 16 Aug 2022 23:59:59 UTC (expired 2 years 8 months ago)
Authentication: RSA 2048 bits (SHA384withRSA)
 View details
Intermediate certificate
ZeroSSL RSA Domain Secure Site CA | 21acc1d
Not After: 29 Jan 2030 23:59:59 UTC (expires in 4 years 8 months)
Authentication: RSA 4096 bits (SHA384withRSA)
 View details
Intermediate certificate
USERTrust RSA Certification Authority | 68b9c76
Not After: 31 Dec 2028 23:59:59 UTC (expires in 3 years 7 months)
Authentication: RSA 4096 bits (SHA384withRSA)
 View details
Root certificate
AAA Certificate Services | d7a7a0f
Not After: 31 Dec 2028 23:59:59 UTC (expires in 3 years 7 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

Good
Certificate chain is correct
Good. This chain contains all the right certificates and in the right order.

DANE (443)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Cookies

Cookies are small chunks of text that are sent between your browser and a website. They are often essential to the operation of the site and sometimes contain sensitive information. Session cookies sent from secure sites must be explicitly marked as secure to prevent being obtained by active network attackers.

Test passed
Everything seems to be well configured. Well done.

HTML Content

On virtually all web sites, HTML markup, images, style sheets, JavaScript, and other page resources arrive not only over multiple connections but possibly from multiple servers and sites spread across the entire Internet. For a page to be properly encrypted, it’s necessary that all the content is retrieved over HTTPS. In practice, that’s very often not the case, leading to mixed content security problems.

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.

Encryption of Embedded Resources

In this section we look at the transport security of all embedded resources. Mixed active content occurs when there are unprotected scripts or styles embedded in a page. This is typically not allowed by modern browsers. Mixed passive content (images, videos and such) are typically allowed, but shouldn't be present.

0 script(s)
  0 out of 0 are secure
0 CSS file(s)
  0 out of 0 are secure
0 media file(s)
  0 out of 0 are secure

Encryption of Outbound Links

Ideally, an encrypted page should only have links that lead to other encrypted pages. If plaintext links are used, passive network attackers can see where people go after they visit your web site. It's also possible that some sensitive information is leaked in the Referer header.

2 link(s)
  0 out of 2 are encrypted
http://nginx.org/
http://nginx.com/
 View all

Analysis

Warning
Plaintext outbound links in HTTPS page
When outbound links are not encrypted, a passive network attacker can see where your users go after visiting your web site.

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) vastly improves security of the network encryption layer. With HSTS enabled, browsers no longer allow clicking through certificate warnings errors, which are typically trivial to exploit. Additionally, they will no longer submit insecure (plaintext) requests to the site in question, even if asked.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

HSTS Policy

URL from which this policy was obtained.Location https://kloon.work.gd/

Analysis

Powerup!
No parent protection
This host could benefit from further protection if the apex hostname would be configured with a HSTS policy that uses 'includeSubDomains'. Enabling HSTS on an entire domain name is the only approach that provides robust security.

Analysis

Powerup!
Deploy HSTS on this host
This host doesn't use HSTS, which means that its users can be easily attacked via MITM attacks. Consider deploying HSTS to disable certificate warnings and increase content and cookie security.

HTTP Public Key Pinning

HTTP Public Key Pinning (HPKP) enables site operators to restrict which certificates are considered valid for their domain names. With a valid HPKP configuration, sites can defeat man in the middle (MITM) attacks using fraudulent or misissued certificates. HPKP is an advanced feature, suitable for use by only high-profile web sites.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Content Security Policy

Content Security Policy (CSP) is a security mechanism that allows web sites control how browsers process their pages. In essence, sites can restrict what types of resources are loaded and from where. CSP policies can be used to defend against cross-site scripting, prevent mixed content issues, as well as report violations for investigation.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Subresource Integrity

Subresource Integrity (SRI) is a new standard that enables browsers to verify the integrity of embedded page resources (e.g., scripts and stylesheets) when they are loaded from third-party web sites. With SRI deployed, remote resources can be used safely, without fear of them being modified by malicious parties.

Test passed
Everything seems to be well configured. Well done.
No external scripts
  SRI not needed
No external stylesheets
  SRI not needed

Analysis

Good
No remote resources
The homepage of this site doesn't contain any remote resources so SRI is not needed.

Expect CT

Expect-CT is a deprecated response HTTP header designed to enable web sites to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that supported this header will submit reports to the specified reporting endpoint. Chrome was the browser that introduced support for this response header, but later deprecated it and removed it in version 107.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Analysis

Powerup!
Deploy Expect-CT to enable reporting
An Expect-CT policy enables web sites to monitor for any problems related to their Expect-CT compliance, detecting potentially serious issues quickly. When issues arise, compliant browsers will submit reports to the specified reporting endpoints. Before CT became required for all public certificates the Expect-CT was also used to require CT, but that use case no longer applies.

Frame Options

The X-Frame-Options header controls page framing, which occurs when a page is incorporated into some other page, possibly on a different site. If framing is allowed, attackers can employ clever tricks to make victims perform arbitrary actions on your site; they do this by showing their web site while forwarding the victim's clicks to yours.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

XSS Protection

Some browsers ship with so-called XSS Auditors, built-in defenses against XSS. Although these defenses work against simple reflective XSS attacks, they can be abused by skillful attackers to add weaknesses to otherwise secure web sites. These dangers are present in both filtering and blocking modes. At this time, the Safari browser ships with its XSS defenses enabled by default. For this reason, the best approach is to explicitly disable this functionality.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Analysis

Powerup!
Explicitly disable browser XSS protection
For best security, every web site should explicitly disable browser-based XSS protection. This is because this type of functionality can be used to introduce vulnerabilities into otherwise error-free web sites.

Content Type Options

Some browsers use a technique called content sniffing to override response MIME types provided by HTTP servers and interpret responses as something else (usually HTML). This behavior, which could potentially lead to security issues, should be disabled by attaching an X-Content-Type-Options header to all responses.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.