SSL-Tools

SSL check results of thor.anderfeld.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for thor.anderfeld.com 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 Wed, 09 Oct 2024 00:30:43 +0000

The mailservers of thor.anderfeld.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @thor.anderfeld.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
thor.anderfeld.com
172.232.50.58
 -
supported
thor.anderfeld.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
thor.anderfeld.com
2600:3c07::f03c:94ff:fed8:34b4
 -
supported
thor.anderfeld.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @thor.anderfeld.com address so far. Test mail delivery

Certificates

First seen at:

CN=thor.anderfeld.com

Certificate chain
  • thor.anderfeld.com
    • 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)
  • thor.anderfeld.com
Alternative Names
  • thor.anderfeld.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
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
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8E:B2:47:A2:5F:4C:60:70:CD:48:75:47:DB:23:11:6F:95:AF:B0:0A:7A:E6:69:55:4B:12:C6:B7:A2:8F:66:E7
SHA1
57:38:B5:10:D7:BD:26:AE:0B:A8:32:E9:E3:8B:C7:CD:A6:69:ED:66
X509v3 extensions
subjectKeyIdentifier
  • 4E:3C:1D:3D:F0:FC:DE:F0:6C:E8:22:7B:68:E1:32:FD:33:31:04:C9
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 9 00:27:51.398 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A3:1D:A8:57:FC:35:84:6C:9B:5C:D4:
  • CB:55:ED:32:E1:FF:97:5B:95:5B:7F:29:4D:0D:3F:54:
  • FD:26:47:1C:81:02:21:00:B6:26:3E:15:AB:BD:EC:55:
  • 2C:06:A5:8B:FF:0B:30:38:0B:F5:4E:17:D5:86:F9:0E:
  • 46:CD:FC:89:B7:93:C9:26
  • 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:27:51.450 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:54:BE:9B:C5:67:31:25:95:A1:7D:7F:73:
  • B9:B1:76:8C:F2:0C:A5:20:52:A2:3B:4A:78:B7:15:39:
  • 69:EF:7D:2D:02:21:00:B5:46:87:95:D1:A4:92:16:4D:
  • 3E:D3:6A:62:89:E1:BC:E6:EC:C5:F9:81:35:40:3F:31:
  • F2:6C:2A:C8:CC:41:96