C
weak
Protocol
https
Domain
dela.enkoping.se
Checked IP
83.243.30.214
Check Time
2024-05-18T06:04:27+02:00
Cache Time
2024-05-03T19:51:02+00:00

Protocol HTTPS (TLS)

Transport Layer Security (TLS) is a secure data transfer protocol that creates secure communication to leverage higher privacy. Widely used on the Internet, it is the successor of the ancient SSL. Several versions of the protocol are used in applications and services, TLS 1.3 is the most recent, but TLS 1.2 is very common too. Many protocols rely on TLS, for instance, the HTTPS (Hypertext Transfer Protocol Secure) is a security layer over the unencrypted HTTP, but several e-mail protocols (eg: IMAPS, SMTPS, POP3S) use as well to get a secure connection.
▼
Cipher suites
C
▼
Highlighted findings
C
Weak Encryption Algorithm (ARIA)
Encryption algorithm ARIA[313][314][315][316] is a block cipher[78][79][80][81] which is considered secure[317], but leading client applications do not use this algorithm. Unless your application or requirements specifically call for their use, it is generally safer to avoid cipher suites that are not adopted and supported by a critical mass of the industry. 
Remove the cipher suite from the list of cipher suites supported by your server.
C
Weak Forward Secrecy (non forward secret algorithm)
Key exchange method has no forward secrecy[127][128][129][130], and does not protect past sessions against future compromises. If long-term secret keys or passwords are compromised, encrypted communications and sessions recorded in the past can be retrieved and decrypted. 
Remove the cipher suite from the list of cipher suites supported by your server.
C
Weak Key Exchange Algorithm (RSA)
RSA[443][444] key exchange is a key exchange[133] that has no forward secrecy[127][128][129][130], and does not protect past sessions against future compromises. If long-term secret keys or passwords are compromised, encrypted communications and sessions recorded in the past can be retrieved and decrypted. Throughout its history RSA encryption has had many security flaws[445][446][447][448][449][450] and was affected by variety of attack types: chosen-ciphertext attack[55] (eg: Bleichenbacher's attack[1][2], ROBOT attack[18][19][20][21]), side-channel attack[69][70][71] (eg: padding oracle attack[63][64][65][66], like Bleichenbacher's cat[3][4][5][6]). 
Always prefer cipher suites with PFS property over the non-PFS ones. Note that performance considerations implies preferring Ephemeral Elliptic-curve Diffie–Hellman[432][433] over Ephemeral Diffie-Hellman[405][406][407][408].
B
Moderate Encryption Algorithm (Camellia)
Encryption algorithm Camellia[318][319][320][321] is a block cipher[78][79][80][81] which is considered secure[322][323], but leading client applications do not use this algorithm. Unless your application or requirements specifically call for their use, it is generally safer to avoid cipher suites that are not adopted and supported by a critical mass of the industry. 
Remove the cipher suite from the list of cipher suites supported by your server.
B
Moderate Encryption Algorithm (SEED)
Encryption algorithm SEED[384][385][386] is a block cipher[78][79][80][81] which is considered secure[387], but leading client applications do not use this algorithm. Unless your application or requirements specifically call for their use, it is generally safer to avoid cipher suites that are not adopted and supported by a critical mass of the industry. 
Remove the cipher suite from the list of cipher suites supported by your server.
B
Moderate TLS Cipher Suite Preference (client cipher suites are preferred insecurely)
Server prefers client's cipher suite[189][190] order over its own cipher suite preference order. It may cause that less secure cipher suite is choosen in case of an improperly configured client. Server should prefer its own cipher suite preference order until it support any intermediate or backward compatible cipher suite. 
Set preference of server cipher suite order or remove any intermediate or backward compatible cipher suite.
A-
Good MAC Algorithm (SHA-1)
message authentication code[135][136][137][138] is a hashed message authentication code[139][140][141][142][143][144][145] which is considered secure[462], despite the fact that the underlayingcryptographic hash function[94][95][96][97] (Secure Hash Algorithm 1[202][203][204]) is considered insecure[205][206][207][208][209][210][211]. 
If your application or requirements specifically call for the use of a message authentication code[135][136][137][138] that does not provide authenticated encryption[74] prefer block cipher mode of operation[82][83][84][85][86] (eg: counter with CBC-MAC[32][33][34], Galois/Counter Mode[46][47][48][49] or message authentication code[135][136][137][138] (eg: Poly1305[458][459]) that proved authenticated encryption over the ones which does not provide it. In case of a hashed message authentication code[139][140][141][142][143][144][145] prefer message authentication code[135][136][137][138] based on Secure Hash Algorithm 2[212][213][214] over the ones based on Secure Hash Algorithm 1[202][203][204].
▶
Checked facts
▶
Detailed info
▼
Key exchange
A
▼
Highlighted findings
Congratulations! We could not find any potential issues regarding your server configuration.
▶
Checked facts
▶
Detailed info
▼
Public keys
C
▼
Highlighted findings
C
Weak Public Key Revocation Check (OCSP stapling not supported)
Server does not support revocation check mechanism Online Certificate Status Protocol (OCSP) stapling[527][528][529][530][531]. Revocation check mechanisms of X.509 public key[493][494][495][496][497] certificates have many flaws [518][519][520][521] and now, the only practically working and used vendor independent mechanisms is OCSP stapling.Without using a certificate revocation check mechanism a client applications (eg: browser, email client, ...), cannot determine whether X.509 public key the server provides still valid or it has already been revoked by the issuer of the certificate. Without this information it cannot be reliably proved that message caomes from the stated sender (its authenticity) or it has been changed, so connections could be open for a man-in-the-middle attack[61]. 
Always chose certificate authority[88][89][90]s which support Online Certificate Status Protocol (OCSP)[522][523][524][525][526]. Prefer server implementations which support Online Certificate Status Protocol (OCSP) stapling[527][528][529][530][531] or use a proxy application make up for this shortcomings.
▶
Checked facts
▶
Detailed info
▼
Versions
C
▼
Highlighted findings
C
Weak TLS/SSL Protocol Version (TLS 1.0)
The Transport Layer Security 1.0[235][236] is a deprecatedearly TLS versions[250][251][252][253][254] cryptography protocol[98]. Payment Card Industry Security Standards Council[472][473] suggests that organizations migrate from TLS 1.0 to TLS 1.1 or higher before June 30, 2018. In October 2018, Apple, Google, Microsoft, and Mozilla jointly announced they would deprecate TLS 1.0 and 1.1 in March 2020. In March 2021 Internet Engineering Task Force[467][468] deprecated TLS 1.0 and 1.1 in RFC 8996. 
Remove the TLS 1.0 and 1.1 version from the list of TLS versions accepted by your server.
C
Weak TLS/SSL Protocol Version (TLS 1.1)
The Transport Layer Security 1.1[237][238] is a deprecatedearly TLS versions[250][251][252][253][254] cryptography protocol[98]. Payment Card Industry Security Standards Council[472][473] suggests that organizations migrate from TLS 1.0 to TLS 1.1 or higher before June 30, 2018. In October 2018, Apple, Google, Microsoft, and Mozilla jointly announced they would deprecate TLS 1.0 and 1.1 in March 2020. In March 2021 Internet Engineering Task Force[467][468] deprecated TLS 1.0 and 1.1 in RFC 8996. 
Remove the Transport Layer Security 1.0[235][236] and 1.1 version from the list of TLS versions accepted by your server.
▶
Checked facts
▶
Detailed info