SSL-Tools

SSL check results of netzbiotop.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for netzbiotop.org 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 Wed, 24 Apr 2024 18:13:22 +0000

The mailservers of netzbiotop.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @netzbiotop.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.flpk.zentralwerk.org
2a0f:5382:acab:1400::a8
 10
supported
mail.flpk.zentralwerk.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
4 s
mail.flpk.zentralwerk.org
45.158.40.168
 10
supported
mail.flpk.zentralwerk.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.flpk.zentralwerk.org

Certificate chain
  • mail.flpk.zentralwerk.org
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.flpk.zentralwerk.org
Alternative Names
  • mail.flpk.zentralwerk.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-13
Not valid after
2024-07-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
03:09:53:F1:AC:FB:D3:8D:54:0C:D4:9B:0E:2A:25:8F:54:A0:BE:7D:06:E7:5B:86:9C:86:C6:48:0E:6A:AF:F6
SHA1
23:7C:07:06:00:3F:B6:C6:F1:AE:9B:EC:30:D7:DB:A3:CF:85:E9:48
X509v3 extensions
subjectKeyIdentifier
  • 06:3C:58:A2:D9:08:9E:68:A5:16:58:90:AD:AF:A2:9A:03:F5:16:A5
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Apr 13 13:20:33.448 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A9:F7:72:01:69:DF:25:08:74:3A:A4:
  • 86:63:22:63:41:C1:2B:AA:6D:1F:BE:29:36:28:09:0B:
  • 6A:9D:1F:6A:51:02:21:00:9F:2C:C3:7A:E6:F6:91:44:
  • 8A:B7:28:31:8C:7E:44:22:96:73:66:40:5E:DC:69:AE:
  • EE:85:D7:37:55:66:57:28
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 13 13:20:33.534 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E9:2E:CE:37:40:0D:25:A4:B8:7A:54:
  • 1E:1B:29:EF:E3:CB:1A:D0:7E:E9:01:3B:B6:7B:A5:DE:
  • E8:F2:EE:0F:66:02:20:48:0F:06:81:3F:B3:F0:E5:E1:
  • 9F:11:C6:B9:61:FB:AB:4D:4D:63:31:21:74:E8:D3:31:
  • 45:EE:13:CD:3F:6D:5D