SSL-Tools

SSL check results of mail.nitzler.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.nitzler.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 Tue, 06 May 2025 09:18:09 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.nitzler.de
136.243.42.167
 -
supported
mail.nitzler.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.nitzler.de
2a01:4f8:212:aa1::2
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.nitzler.de

Certificate chain
  • mail.nitzler.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.nitzler.de
Alternative Names
  • imap.bgn-it.de
  • imap.nitzler.de
  • mail.bgn-it.de
  • mail.nitzler.de
  • smtp.bgn-it.de
  • smtp.nitzler.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-05-06
Not valid after
2025-08-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EF:31:A4:F1:7F:CD:C5:3D:01:E0:3A:DB:58:72:88:A5:94:8F:6F:80:07:A4:27:FB:60:30:8A:D3:3A:F9:AB:75
SHA1
94:7F:3F:D6:50:39:32:E1:DC:CC:BB:CF:D0:70:35:BB:81:5A:E3:4C
X509v3 extensions
subjectKeyIdentifier
  • D4:AF:D2:1A:CA:4F:20:6D:F3:7A:BA:D5:E1:9B:CA:9F:8F:51:83:AB
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/15.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : May 6 08:31:08.826 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:60:E3:30:93:C1:4B:A6:64:FA:DC:9A:0E:
  • 87:86:C1:30:FE:CC:AE:FD:49:1A:01:B8:55:01:10:FC:
  • 88:4C:D8:6C:02:21:00:86:10:74:57:F0:0D:5D:65:ED:
  • 3E:6F:BE:35:D6:95:32:C3:56:7D:FE:30:91:24:05:CA:
  • 78:7D:A8:FC:F5:E9:01
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : May 6 08:31:09.595 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7A:84:3E:63:4F:CC:BB:D7:3D:70:3E:76:
  • CB:B3:24:22:99:EF:B7:40:0D:9C:12:CC:C5:7D:4E:57:
  • AA:2C:11:98:02:20:4E:44:5C:A2:90:83:CE:52:20:18:
  • C2:9E:0C:A8:62:97:B4:B9:8B:F4:50:B8:34:7E:A2:72:
  • 7E:3A:90:21:CE:48