SSL-Tools

SSL check results of imst.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for imst.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 Wed, 12 Jun 2024 11:24:39 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx0.imst.de
195.243.247.247
 10
supported
mx0.imst.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
61 s
mail.imst.de
195.243.247.110
 15
supported
mail.imst.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
61 s
mxbackup.imst.de
94.79.138.147
Results incomplete
50 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 @imst.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.imst.de

Certificate chain
  • mail.imst.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.imst.de
Alternative Names
  • mail.imst.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-11
Not valid after
2024-07-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F1:D1:9E:44:56:7D:37:7A:57:51:67:2B:1A:8E:1F:3E:29:66:A4:13:26:7A:CC:35:CE:E1:E4:80:0C:91:CE:B7
SHA1
45:34:DB:DF:6E:CC:95:82:93:27:0A:68:E2:C0:7D:76:70:32:47:40
X509v3 extensions
subjectKeyIdentifier
  • 67:DD:D8:12:C3:ED:6E:F2:A1:B7:16:FC:57:5E:63:D9:11:96:DD:19
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Apr 11 01:02:08.013 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5E:7E:FA:07:AE:9E:1E:95:06:3F:27:33:
  • 9F:00:79:3B:AB:57:E8:07:E9:F0:B3:F1:E9:E4:20:E7:
  • 30:F1:04:E1:02:21:00:92:B7:C0:1D:EC:A6:A5:6F:BE:
  • 4C:1C:84:F9:99:43:B5:AD:67:25:5F:0A:12:E3:3D:71:
  • F2:77:31:AA:C9:1D:2B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Apr 11 01:02:08.109 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:47:2A:97:73:C0:EF:B2:8F:2E:BD:68:52:
  • 8A:BC:95:3F:98:10:8F:A6:1C:88:51:FE:EB:F7:DA:48:
  • C4:F5:C4:11:02:20:7D:14:39:7F:09:1A:88:C4:A2:EB:
  • 9C:93:A6:D4:60:2D:87:AA:C0:95:22:AC:34:FC:C2:02:
  • F5:43:B4:26:C6:43
First seen at:

CN=mx0.imst.de

Certificate chain
  • mx0.imst.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx0.imst.de
Alternative Names
  • mx0.imst.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-06-12
Not valid after
2024-09-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A4:CF:82:C3:44:3C:D4:EB:88:60:53:4C:86:CD:C6:72:32:CC:3B:EB:5F:10:D1:A1:69:22:33:23:0E:35:A4:E7
SHA1
DF:2E:71:F1:62:0B:C0:63:29:14:2F:2B:EE:0D:C0:6D:61:50:01:C9
X509v3 extensions
subjectKeyIdentifier
  • D6:0F:2F:79:77:D8:79:E2:BF:26:5F:E8:8A:19:62:45:F0:F4:3C:C0
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Jun 12 09:13:10.898 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:20:E4:4D:52:6B:1B:25:CC:33:B8:E6:10:
  • E0:D9:B4:F4:BC:10:F5:02:E3:59:DA:68:3F:01:84:5A:
  • 36:7E:18:60:02:20:1C:6A:DE:6B:8E:41:98:EC:4A:37:
  • CF:89:BC:BC:0A:A4:80:66:AF:F0:C5:71:0E:0C:20:29:
  • 03:81:C0:CE:A2:20
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Jun 12 09:13:10.965 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:04:93:09:43:45:C2:7F:EC:D6:C7:FB:0E:
  • 66:69:29:E8:17:C7:13:E9:79:F8:FD:B5:05:9F:7D:A0:
  • E1:50:B4:03:02:21:00:B1:B0:70:61:EA:23:B8:01:90:
  • 3D:39:ED:4B:3A:DF:4D:BF:37:7E:05:BC:BD:90:59:E5:
  • EB:19:ED:A0:B1:02:06