SSL-Tools

SSL check results of gut-obermuehle.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for gut-obermuehle.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 Sat, 27 Apr 2024 15:38:53 +0000

The mailservers of gut-obermuehle.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @gut-obermuehle.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
2 s

Outgoing Mails

We have not received any emails from a @gut-obermuehle.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
2024-04-03
Not valid after
2024-07-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
14:B6:CB:94:85:77:15:A6:62:18:14:A8:B4:A0:D7:EF:C7:4D:65:66:A6:83:D0:E2:DC:45:AB:C0:D1:8F:7A:45
SHA1
1E:3B:EF:C5:2A:5E:9F:1C:74:7B:D6:9B:2B:F6:6C:91:B2:08:AB:90
X509v3 extensions
subjectKeyIdentifier
  • 00:25:7B:42:4A:1E:F3:0B:32:3B:12:69:78:88:9D:FD:27:6F:7F:0D
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 : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Apr 3 22:01:20.412 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6D:D9:87:03:5F:D5:BD:76:65:27:BE:C0:
  • 8E:11:9D:EA:45:5B:17:29:34:21:02:03:48:09:94:A1:
  • 64:81:35:3E:02:21:00:80:40:78:1B:49:66:CA:55:4E:
  • 1D:9B:AF:00:67:26:F1:38:56:C5:BA:C6:80:47:21:C5:
  • EA:5C:FB:98:10:C9:F2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Apr 3 22:01:20.604 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BD:B5:F7:A3:B7:50:86:80:F7:33:15:
  • 6F:2A:4E:3C:20:23:CB:91:81:0D:B9:40:1F:67:22:BF:
  • D6:4B:77:4B:10:02:20:10:10:9D:E4:16:3A:9D:76:50:
  • 2E:B4:6F:04:17:11:30:54:71:53:69:4A:C8:A2:16:75:
  • 43:00:9E:AE:1A:B9:5D