SSL-Tools

SSL check results of mail.seccore.io

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.seccore.io 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 Sat, 05 Sep 2026 00:30:27 +0000

The mailservers of mail.seccore.io can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.seccore.io addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.seccore.io
146.59.85.198
 -
supported
mail.seccore.io
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.seccore.io
2001:41d0:602:4ac6::100
 -
supported
mail.seccore.io
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 @mail.seccore.io address so far. Test mail delivery

Certificates

First seen at:

CN=mail.seccore.io

Certificate chain
  • mail.seccore.io
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.seccore.io
Alternative Names
  • hosting.seccore.io
  • mail.seccore.io
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-08-21
Not valid after
2026-11-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
9A:AB:E0:D7:6C:0E:13:8E:BA:EB:43:0F:18:29:B3:00:E4:94:0C:04:FE:1B:2B:F1:15:FA:B2:22:87:4B:70:6C
SHA1
C7:F0:00:54:F7:E5:BF:06:81:2C:A6:EB:9A:E3:74:81:F9:39:C7:BE
X509v3 extensions
subjectKeyIdentifier
  • 18:B8:14:98:35:47:7C:59:22:86:8A:C8:E8:9A:D0:D1:2E:43:3E:F4
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/95.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:AF:86:3D:3B:3E:E5:9F:A5:77:DE:A8:24:5D:36:B0:
  • D9:ED:22:A2:23:F4:61:77:41:22:94:52:EE:95:50:5F
  • Timestamp : Aug 21 21:51:41.152 2026 GMT
  • Extensions: 00:00:05:00:18:91:40:96
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:27:3C:EA:F7:FF:F9:CC:69:ED:50:29:10:
  • D8:DC:43:98:28:88:FD:91:9C:6A:A2:70:56:10:D7:76:
  • 3B:CE:F3:10:02:20:65:87:3D:74:02:6F:41:FE:8F:BB:
  • E4:20:EB:50:59:2C:AE:80:25:B3:4D:51:3C:86:0B:78:
  • B5:EF:89:10:E8:35
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D7:6D:7D:10:D1:A7:F5:77:C2:C7:E9:5F:D7:00:BF:F9:
  • 82:C9:33:5A:65:E1:D0:B3:01:73:17:C0:C8:C5:69:77
  • Timestamp : Aug 21 21:51:41.063 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CA:E2:1D:22:CE:28:1D:D8:07:BF:C2:
  • D6:50:C1:D7:A8:49:17:34:F1:7E:6F:E2:38:C3:63:17:
  • 35:E4:A8:B3:6D:02:20:63:26:D6:34:2A:02:12:6C:D1:
  • 4A:B1:C9:26:43:68:8A:42:C0:68:57:78:53:D1:88:95:
  • 21:42:AF:F0:98:D3:15