SSL-Tools

SSL check results of securityfile.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for securityfile.net 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 Mon, 17 Mar 2025 02:56:38 +0000

We can not guarantee a secure connection to the mailservers of securityfile.net!

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

/mailservers/securityfile.net

Servers

Incoming Mails

These servers are responsible for incoming mails to @securityfile.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.securityfile.net
96.68.9.6
Results incomplete
0
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
securityfile.net
96.68.9.6
 10
supported
smtp.securityfile.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
29 s

Outgoing Mails

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

Certificates

First seen at:

CN=smtp.securityfile.net

Certificate chain
  • smtp.securityfile.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • smtp.securityfile.net
Alternative Names
  • smtp.securityfile.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-02-04
Not valid after
2025-05-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8C:BE:08:4F:1C:64:4C:8A:15:53:0D:D9:1D:8E:B0:95:6D:18:CF:EB:E4:04:65:A4:45:21:61:91:B2:76:65:C3
SHA1
2F:1F:43:1B:50:BC:FB:EE:6B:F9:7A:69:A9:91:97:F6:E9:79:CC:4C
X509v3 extensions
subjectKeyIdentifier
  • C9:65:F0:F4:CC:FF:73:1F:88:52:F9:1D:8B:3A:5A:68:C0:53:17:0E
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 : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Feb 4 21:58:00.875 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8D:90:C6:C4:FB:EB:1F:BF:D6:22:90:
  • 22:89:35:3F:85:F4:1A:71:A0:25:69:E6:25:18:3C:30:
  • 5A:E8:BA:2E:5E:02:21:00:A6:05:9A:69:1C:81:EF:AD:
  • 2B:BD:BB:FC:4B:85:68:69:60:5D:62:70:18:52:59:6E:
  • 97:85:73:86:80:9D:09:59
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Feb 4 21:58:01.017 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:18:72:5D:2A:65:34:42:71:E3:7B:A2:A6:
  • 79:8E:80:05:86:8E:1A:3F:51:9A:B5:C9:5C:93:5E:D6:
  • 13:55:7D:A0:02:21:00:DA:D6:02:28:B6:F1:0F:CB:74:
  • 71:61:0C:DE:2A:84:99:1C:53:87:16:42:CC:08:1A:A6:
  • E3:82:0B:EB:A4:46:AE