SSL check results of epilepsie-vereinigung.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for epilepsie-vereinigung.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

Report created Sun, 15 May 2022 16:32:12 +0000

The mailservers of epilepsie-vereinigung.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @epilepsie-vereinigung.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx00.udag.de
62.146.106.39
10
supported
mx00.udag.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mx01.udag.de
62.146.106.40
20
supported
mx00.udag.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx00.udag.de

Certificate chain
  • mx00.udag.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)
  • mx00.udag.de
Alternative Names
  • mx00.udag.de
  • mx01.udag.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-04-28
Not valid after
2022-07-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
46:F8:8E:14:A8:3B:F3:C2:55:4E:5C:A4:E6:AD:35:80:D2:6D:08:6D:D4:51:9B:27:A3:B9:F8:F4:E7:C5:26:D4
SHA1
31:E8:72:2F:B0:CF:85:68:F1:3B:11:A4:A2:97:8F:F6:0C:05:18:38
X509v3 extensions
subjectKeyIdentifier
  • 45:86:55:F4:BD:3D:90:C7:D8:94:95:64:B9:DA:F4:AB:94:F6:1E:90
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 : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
  • 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
  • Timestamp : Apr 28 22:01:21.053 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:77:2A:74:98:2F:75:EA:23:5F:F1:88:93:
  • D2:C1:25:7A:CC:3D:44:40:3F:AF:B5:26:3C:7F:69:59:
  • F1:68:D8:85:02:20:17:84:EB:84:58:E2:46:1B:F3:ED:
  • DF:E5:DD:0B:9E:02:4C:EC:2E:AF:3A:DD:39:C9:A4:1B:
  • 1F:FC:17:CE:3C:E1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Apr 28 22:01:21.360 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1E:55:D6:FD:F1:49:B7:FC:EE:B3:F5:44:
  • 38:99:20:0B:CD:CA:48:15:78:06:ED:60:F2:76:18:A9:
  • 8E:5A:DA:44:02:21:00:D5:47:65:6F:FE:F5:9E:81:6A:
  • 39:34:FB:01:C3:B2:DC:3E:7C:C6:63:C7:B1:BE:09:14:
  • E3:2D:79:09:66:DD:3C