SSL-Tools

SSL check results of tiefensee.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for tiefensee.org 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 Fri, 04 Oct 2024 00:30:22 +0000

The mailservers of tiefensee.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @tiefensee.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.tiefensee.org
2a01:7e0:0:405::18ec
 0
supported
tiefensee.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
mail.tiefensee.org
31.172.93.62
 0
supported
tiefensee.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=tiefensee.org

Certificate chain
  • tiefensee.org
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • tiefensee.org
Alternative Names
  • imap.tiefensee.org
  • mail.tiefensee.org
  • smtp.tiefensee.org
  • tiefensee.org
  • www.tiefensee.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-08
Not valid after
2024-12-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
89:0F:BA:8C:C9:33:5C:DF:AF:1E:F1:2F:7D:91:20:80:53:51:16:8E:31:91:16:42:85:80:52:48:FD:F8:38:53
SHA1
C3:CC:7D:09:73:0C:2B:C0:28:42:F4:FB:7F:A1:69:F9:50:32:DA:20
X509v3 extensions
subjectKeyIdentifier
  • 6B:60:08:04:1C:2F:90:A7:31:C6:00:82:34:A6:98:8D:CD:B7:35:5A
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.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 9 00:43:43.551 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0C:D5:ED:BF:89:35:0D:5B:BC:38:37:B7:
  • 79:20:B2:0F:D1:E3:F8:B3:82:70:E5:2C:11:C4:2F:13:
  • 77:51:4A:E0:02:20:06:F5:DB:41:5C:23:3B:A1:C0:67:
  • 75:B6:F8:E2:EC:CA:49:DE:DE:02:30:96:E3:A8:E0:99:
  • F5:CD:34:B9:5F:8D
  • 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 : Sep 9 00:43:43.567 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:48:38:1F:29:34:35:41:AB:3A:2A:42:C1:
  • 71:EA:C3:0A:33:F4:54:AC:64:F4:84:A6:E1:51:CB:9A:
  • 2D:A8:2C:24:02:21:00:F6:01:17:BF:C5:62:58:D9:1A:
  • 48:C6:3A:22:62:F0:2C:2F:B9:40:8D:31:0E:55:10:9C:
  • DD:AA:A2:28:71:DB:DC