SSL check results of mail.spiderx.co

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.spiderx.co 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 Tue, 24 Sep 2024 13:21:28 +0000

The mailservers of mail.spiderx.co can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.spiderx.co addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spiderx.co
185.66.91.158
-
supported
mail.spiderx.co
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.spiderx.co

Certificate chain
  • mail.spiderx.co
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mail.spiderx.co
Alternative Names
  • mail.spiderx.co
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-07-28
Not valid after
2024-10-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
81:CC:77:87:75:C5:81:CB:9A:A9:AF:37:8D:DB:BC:71:E8:E8:9E:94:7F:72:10:CD:CD:F4:B3:14:B9:1E:97:D2
SHA1
93:C0:88:35:39:06:1E:B3:D1:F1:3F:E0:09:9B:36:53:D5:B9:E6:EF
X509v3 extensions
subjectKeyIdentifier
  • 56:56:B4:B1:60:0C:55:38:E9:6E:82:F3:95:28:2B:B3:1B:1B:EB:C5
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.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 : Jul 28 12:34:58.836 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D3:92:74:29:5B:24:29:09:98:B5:7E:
  • 78:44:27:F9:97:4B:6E:03:7C:61:82:C6:0A:07:B6:FB:
  • B2:25:24:14:61:02:21:00:D2:34:F8:BC:52:72:F2:66:
  • D3:36:A3:47:8B:5E:B3:C6:45:D1:58:22:BF:EA:67:81:
  • E2:80:84:C5:A0:5F:6C:E6
  • 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 : Jul 28 12:34:58.877 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:13:BA:30:78:93:DA:FD:93:4D:C0:AF:00:
  • EB:36:2F:2D:B4:27:E5:DE:38:C4:E7:F5:5A:E4:64:80:
  • C5:AE:69:33:02:21:00:DC:B4:CE:37:83:8A:FE:4B:ED:
  • 45:94:D5:0B:0F:AA:DF:4E:4C:0D:72:57:4B:4E:03:E7:
  • 8D:50:18:F0:7E:A1:3E

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.spiderx.co
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
error
Debug
valid