SSL-Tools

SSL check results of berling.be

NEW You can also bulk check multiple servers.

Discover if the mail servers for berling.be can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

JSON Refresh

Report created Fri, 23 Oct 2020 18:43:41 +0000

We can not guarantee a secure connection to the mailservers of berling.be!

Please contact the operator of berling.be and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/berling.be

Servers

Incoming Mails

These servers are responsible for incoming mails to @berling.be addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.karottika.de
2a01:4f8:121:2321:1::25
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.karottika.de
2a01:4f8:121:2321:1::53
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.karottika.de
178.63.73.57
 10
supported
mail.karottika.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • SSL_RSA_EXPORT_WITH_RC4_40_MD5
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @berling.be address so far. Test mail delivery

Certificates

First seen at:

CN=mail.karottika.de

Certificate chain
Subject
Common Name (CN)
  • mail.karottika.de
Alternative Names
  • mail.karottika.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-10-22
Not valid after
2021-01-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
59:F1:09:78:3E:3F:74:85:EB:AB:8F:E5:C4:04:EB:12:53:12:4C:E1:F1:F8:4C:E5:9A:45:4B:59:50:73:08:0C
SHA1
B9:1E:6B:7F:8A:3E:B5:DC:CA:CE:E8:9F:EC:AD:24:5E:8A:32:A4:5E
X509v3 extensions
subjectKeyIdentifier
  • B6:E1:58:C2:EB:C1:9D:3D:B5:68:71:31:77:79:71:02:80:98:7B:01
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Oct 22 06:05:43.619 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E4:92:3B:21:F5:74:71:8A:06:92:8D:
  • 97:0E:4F:24:CC:4B:90:7B:57:8C:87:06:5A:A2:F7:56:
  • EA:8F:68:E8:BD:02:21:00:BB:5E:00:7F:4B:DD:31:49:
  • 43:F4:AE:CB:CE:9A:4B:FE:C0:9A:4D:72:A9:3C:22:D9:
  • F4:4E:D1:58:D3:50:26:D0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Oct 22 06:05:43.585 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D0:D0:EA:D7:4B:B9:01:5F:A1:FE:CC:
  • 88:3D:87:41:07:D3:71:A5:66:A6:7F:88:0B:F4:32:82:
  • 32:DA:A4:65:68:02:21:00:B6:89:5F:A9:4B:E9:38:FC:
  • B9:AC:35:7E:FE:CD:ED:51:01:E6:79:39:54:62:D5:E2:
  • 6C:E6:26:8A:BE:F4:6B:77