SSL-Tools

SSL check results of mail.koch.rip

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.koch.rip 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, 24 Sep 2024 12:40:28 +0000

We can not guarantee a secure connection to the mailservers of mail.koch.rip!

Please contact the operator of mail.koch.rip and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/mail.koch.rip

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.koch.rip addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.koch.rip
193.203.238.169
 -
supported
mail.koch.rip
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.koch.rip
fe80::be24:11ff:fe38:d4e
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.koch.rip

Certificate chain
  • mail.koch.rip
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.koch.rip
Alternative Names
  • imap.koch.rip
  • mail.koch.rip
  • smtp.koch.rip
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2024-09-23
Not valid after
2024-12-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C3:DD:88:68:6E:B9:4F:26:46:BF:E5:A2:83:0F:B4:85:F8:B2:F0:F0:88:40:98:6E:B5:8D:2A:15:43:37:B8:65
SHA1
E2:75:17:62:30:E4:AA:5F:3B:1D:42:C3:1C:A8:E0:FF:E2:B1:2A:B4
X509v3 extensions
subjectKeyIdentifier
  • 5B:93:70:C2:75:D2:EB:EF:36:ED:E1:33:E7:80:51:77:3B:2F:79:35
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.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 : Sep 23 20:32:36.150 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:41:29:A4:1A:BA:A1:E8:0C:FA:4E:73:28:
  • DC:5A:90:EB:86:3A:CC:6C:6D:7C:86:E1:DB:B3:F1:31:
  • 25:6F:53:D0:02:20:2C:2B:1F:00:75:FD:AF:FA:C6:12:
  • 08:E6:CB:22:28:34:A2:C6:C0:97:70:5E:23:BE:00:DB:
  • AF:5B:A6:7A:88:B2
  • 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 : Sep 23 20:32:36.149 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:98:FB:C0:B5:89:1E:BE:85:BA:A0:23:
  • 73:3B:3E:86:D5:A9:E4:13:F3:76:83:51:42:7A:1F:E5:
  • DA:5C:B2:C0:17:02:20:03:C4:8A:28:2D:C8:D8:CB:E1:
  • A3:17:0E:49:18:B3:A1:73:15:79:ED:CF:42:69:79:2E:
  • 43:EC:E2:26:4C:60:0F