SSL-Tools

SSL check results of resolvecraft.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for resolvecraft.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 Thu, 28 Mar 2024 00:15:47 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.resolvecraft.com
185.104.29.158
 10
supported
mail.resolvecraft.com
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 @resolvecraft.com address so far. Test mail delivery

Certificates

First seen at:

CN=mail.resolvecraft.com

Certificate chain
  • mail.resolvecraft.com
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.resolvecraft.com
Alternative Names
  • mail.resolvecraft.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-26
Not valid after
2024-06-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
54:0D:3B:FD:F8:5E:71:41:F5:42:C4:39:B4:15:2C:B7:0C:34:E7:5B:3D:A1:CD:0D:22:EB:02:C6:4D:34:90:E4
SHA1
CC:C4:E1:4C:7F:89:F2:AA:51:92:AF:9E:02:B4:11:BF:EE:CB:70:43
X509v3 extensions
subjectKeyIdentifier
  • 34:9C:3F:60:57:B9:21:5D:C4:F5:9C:20:89:99:75:DB:92:E0:98:3B
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.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 : Mar 26 19:54:23.650 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:72:CA:48:CC:02:B8:87:A4:15:4F:FB:FE:
  • 38:AC:22:D4:C7:92:7A:40:ED:F9:7C:FE:AC:97:CB:43:
  • D6:FA:99:C1:02:21:00:92:CB:79:E7:EA:88:12:54:CE:
  • F3:A1:46:AD:5B:91:FC:19:92:0E:CF:6F:7A:58:4F:8F:
  • D1:88:99:D4:25:54:E7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 26 19:54:23.637 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:72:47:02:EC:21:5D:FB:17:99:DD:B8:24:
  • 0C:92:AF:67:0B:B2:DE:62:70:1F:79:F5:74:13:10:58:
  • 90:8B:B7:BD:02:20:4C:33:E2:5A:F2:31:BF:C0:E6:F4:
  • 5A:B4:2D:33:B9:BB:63:F0:BB:6B:68:B3:A4:BE:4C:34:
  • FD:26:B0:41:2D:77