SSL-Tools

SSL check results of mail2.gebietsdiener.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail2.gebietsdiener.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 Sun, 17 May 2026 09:06:19 +0000

We can not guarantee a secure connection to the mailservers of mail2.gebietsdiener.de!

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

/mailservers/mail2.gebietsdiener.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail2.gebietsdiener.de
46.38.232.248
Results incomplete
-
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail2.gebietsdiener.de
2a03:4000:2:cf::1
 -
supported
mail2.gebietsdiener.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
36 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail2.gebietsdiener.de

Certificate chain
  • mail2.gebietsdiener.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R13
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail2.gebietsdiener.de
Alternative Names
  • mail2.gebietsdiener.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R13
validity period
Not valid before
2026-04-15
Not valid after
2026-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
FA:26:62:45:E1:AC:A4:38:2F:C2:E8:30:55:89:91:9F:C0:3E:68:5F:D8:F6:15:1C:2C:30:6C:FD:3B:8D:3A:24
SHA1
BE:6F:90:AC:F9:26:A0:A3:C7:F5:40:74:E6:5F:F5:80:91:CD:38:2B
X509v3 extensions
subjectKeyIdentifier
  • A0:A6:AC:4B:A5:DE:DA:29:BF:3E:E3:55:53:A4:FD:86:73:81:D2:E9
authorityKeyIdentifier
  • keyid:E7:AB:9F:0F:2C:33:A0:53:D3:5E:4F:78:C8:B2:84:0E:3B:D6:92:33
authorityInfoAccess
  • CA Issuers - URI:http://r13.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r13.c.lencr.org/100.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:AF:86:3D:3B:3E:E5:9F:A5:77:DE:A8:24:5D:36:B0:
  • D9:ED:22:A2:23:F4:61:77:41:22:94:52:EE:95:50:5F
  • Timestamp : Apr 15 16:54:30.929 2026 GMT
  • Extensions: 00:00:05:00:03:F3:79:AD
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CB:DF:56:44:08:90:18:51:34:94:17:
  • 0F:17:FC:8D:2A:F9:26:D0:9D:26:6F:DA:0C:43:F2:4B:
  • CD:8A:B7:F1:F8:02:20:5B:DF:97:CF:5E:54:6C:BF:AF:
  • FB:DE:8E:94:C8:76:1F:49:F8:E8:95:37:2E:6F:D6:3C:
  • 85:2A:22:3F:61:9F:03
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D8:09:55:3B:94:4F:7A:FF:C8:16:19:6F:94:4F:85:AB:
  • B0:F8:FC:5E:87:55:26:0F:15:D1:2E:72:BB:45:4B:14
  • Timestamp : Apr 15 16:54:30.899 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BD:DD:CB:FA:58:45:A9:3A:6E:EB:E7:
  • 9A:8A:C5:3D:13:35:03:DE:68:4B:5D:C5:CA:46:F8:59:
  • 4A:45:16:B5:04:02:20:60:66:B6:2A:11:41:1A:B5:CD:
  • 5E:32:DE:F7:6F:B7:26:EE:46:4C:5F:AD:FF:95:C8:78:
  • C7:42:89:29:7A:92:53