SSL-Tools

SSL check results of nulldata.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for nulldata.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, 25 Feb 2021 02:11:50 +0000

The mailservers of nulldata.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @nulldata.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.nulldata.de
2a00:1828:2000:82::23
 10
supported
mail.nulldata.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s
mail.nulldata.de
89.238.67.162
 10
supported
mail.nulldata.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.nulldata.de

Certificate chain
  • mail.nulldata.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • mail.nulldata.de
Alternative Names
  • mail.nulldata.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-07
Not valid after
2021-05-08
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
80:BD:6A:3E:04:0F:E5:87:A3:79:55:F4:92:B1:3D:41:F3:B7:92:8A:AF:44:E6:CF:23:44:96:EB:2F:A2:16:89
SHA1
A8:1F:5B:B1:C1:C6:F6:2C:8E:57:33:26:3E:B8:12:FA:D7:C5:5D:63
X509v3 extensions
subjectKeyIdentifier
  • 4C:66:2A:91:96:2B:89:58:C1:9C:05:CE:74:00:77:ED:2F:0E:F4:61
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
  • 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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Feb 7 05:48:33.903 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6D:BA:D5:1B:D2:27:EE:78:1F:C1:0C:B0:
  • 37:9A:CA:30:7A:32:48:F2:7A:6D:37:84:23:A1:45:DD:
  • F7:AD:DB:50:02:20:6B:8E:E8:6A:A5:C3:66:A1:06:67:
  • 9E:24:6F:DC:88:84:AD:91:66:B0:5B:80:BF:74:38:BF:
  • B1:5A:CF:78:DC:21
  • 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 : Feb 7 05:48:33.893 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8F:3D:AE:8B:62:20:9A:5A:F1:C5:EC:
  • 89:CA:7C:3B:47:EE:F0:BD:41:4F:37:7D:E0:A9:CB:EA:
  • 24:E2:4E:25:4A:02:21:00:E1:AF:8F:3D:CE:02:10:D2:
  • 90:F7:94:91:A2:47:47:4C:3A:73:15:FC:30:02:32:53:
  • 19:4F:EA:BD:12:DD:C8:3A