SSL-Tools

SSL check results of srv1.mail.clearsite.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for srv1.mail.clearsite.nl 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:23 +0000

The mailservers of srv1.mail.clearsite.nl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @srv1.mail.clearsite.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
srv1.mail.clearsite.nl
2a03:9700:8000::242
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
srv1.mail.clearsite.nl
31.7.5.242
 10
supported
srv1.mail.clearsite.nl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @srv1.mail.clearsite.nl address so far. Test mail delivery

Certificates

First seen at:

CN=srv1.mail.clearsite.nl

Certificate chain
  • srv1.mail.clearsite.nl
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • srv1.mail.clearsite.nl
Alternative Names
  • srv1.mail.clearsite.nl
  • www.srv1.mail.clearsite.nl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-08-17
Not valid after
2024-11-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B7:FE:F6:AE:7A:B4:7C:C7:68:1E:48:00:D2:E5:64:46:0A:44:1C:40:2D:55:AD:9B:0A:56:47:8D:A9:C0:C3:9A
SHA1
EF:27:23:CC:D7:D0:EF:67:A8:DD:49:D1:3A:3A:AC:56:70:E8:59:42
X509v3 extensions
subjectKeyIdentifier
  • 97:B4:A7:5E:B0:54:03:66:85:3D:EC:F1:6C:1E:C7:41:D1:6E:06:27
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.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 : Aug 17 07:59:41.604 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:22:D3:57:AE:ED:05:63:91:6C:97:75:24:
  • 1B:2D:F7:B4:C8:9A:BE:06:AD:EC:8C:E1:71:EE:75:86:
  • 99:4D:B6:8C:02:21:00:BD:CE:D1:62:2C:DF:48:EF:E2:
  • 72:35:47:75:61:F3:A1:F5:76:0D:DD:DA:81:46:B2:38:
  • 37:9C:59:57:6C:8D:E3
  • 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 : Aug 17 07:59:41.675 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:70:B2:AA:3A:DB:98:46:01:40:8F:2F:F0:
  • 06:D6:9E:6B:87:57:32:5E:8E:68:08:41:51:0F:09:AE:
  • 59:E5:BF:FF:02:21:00:92:F3:73:BA:98:CE:75:A9:A2:
  • 55:55:12:37:62:A2:A9:DE:64:F8:E8:ED:90:4C:F7:25:
  • FE:64:A7:B8:F3:48:F2