SSL-Tools

SSL check results of biestow-info.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for biestow-info.de 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 Thu, 28 Mar 2024 16:33:31 +0000

The mailservers of biestow-info.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @biestow-info.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
cloud-01.biestow-info.de
2a01:4f8:1c1c:15f4::1
 1
supported
cloud-01.biestow-info.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s
cloud-01.biestow-info.de
195.201.143.100
 1
supported
cloud-01.biestow-info.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

We have not received any emails from a @biestow-info.de address so far. Test mail delivery

Certificates

First seen at:

CN=cloud-01.biestow-info.de

Certificate chain
  • cloud-01.biestow-info.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • cloud-01.biestow-info.de
Alternative Names
  • cloud-01.biestow-info.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-28
Not valid after
2024-06-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DE:99:97:DB:2D:5E:D2:6C:99:32:12:57:08:5A:47:0C:72:88:4B:87:2D:EE:23:5B:4E:0B:3A:41:29:2F:F2:68
SHA1
3A:84:A8:A5:79:2C:81:6F:C9:01:EA:CE:7F:D3:F5:64:2A:08:B4:B9
X509v3 extensions
subjectKeyIdentifier
  • 70:CE:ED:E4:D7:D4:BB:B1:F5:35:E7:FC:FA:AF:2E:75:7F:7E:90:17
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 28 13:57:45.618 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E2:8D:A6:5D:91:7E:08:7D:0F:4A:F4:
  • 1D:BF:7B:3B:80:99:CD:0F:CF:25:60:3F:D2:22:6B:85:
  • 35:91:F1:71:6B:02:21:00:FD:39:DF:5E:D5:B8:2C:B1:
  • C9:C6:F9:DF:10:7B:90:50:C2:48:E0:CA:2B:C4:FD:3C:
  • 74:68:4B:78:BB:04:BD:B0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 28 13:57:45.623 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9D:4C:CF:FF:84:BA:C7:A8:89:78:F0:
  • 6C:0C:20:2E:44:57:54:A9:13:D4:50:5F:18:8E:63:C2:
  • 61:93:F4:28:23:02:20:08:A8:44:CC:3D:1E:8D:8F:00:
  • B8:94:D3:DC:C9:63:53:7B:45:58:B5:BE:E1:96:EB:DD:
  • 29:D4:8E:EC:AD:72:E4