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

Report created Mon, 30 Sep 2024 00:30:06 +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
0
supported
smtp.securityfile.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
23 s
securityfile.net
96.68.9.6
Results incomplete
10
unsupported
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 @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

      • 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
2024-09-02
Not valid after
2024-12-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2C:41:D3:F9:A4:62:5F:62:A3:5E:B8:D8:D0:31:AE:85:BD:96:1B:8E:20:7D:58:F2:68:DE:5A:8D:5E:D7:3D:8D
SHA1
83:F1:70:BE:DE:5C:65:EC:73:EC:46:EC:84:21:03:94:D6:B8:99:FE
X509v3 extensions
subjectKeyIdentifier
  • 15:93:F3:00:1B:DF:02:18:67:41:49:DD:B9:F3:02:B8:BF:66:41:5C
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Sep 3 00:28:53.724 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AF:37:89:FA:16:86:8A:D1:B7:36:16:
  • 81:AD:30:04:02:64:9C:1D:3D:61:BF:BE:B1:DE:C7:54:
  • 4E:9A:50:F5:71:02:21:00:98:B9:BD:6F:76:7D:01:ED:
  • F6:D6:25:CE:A3:2E:E6:14:67:EA:05:B3:50:69:39:F6:
  • 3B:00:48:3E:1B:9B:BC:0C
  • 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 : Sep 3 00:28:53.791 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1A:9B:AF:BC:FD:41:3B:EF:6E:F7:C4:05:
  • E2:B0:EA:9A:E8:E2:68:2F:02:B4:44:08:6B:4D:B8:74:
  • AF:3F:31:C4:02:21:00:A8:07:50:0D:EB:C1:B8:E8:63:
  • FB:B3:09:E1:F8:EE:E3:9D:F3:52:85:D7:28:6C:22:73:
  • 43:B4:A1:98:EB:65:D7