SSL-Tools

SSL check results of lynxcore.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for lynxcore.org 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 Tue, 23 Apr 2024 19:20:34 +0000

The mailservers of lynxcore.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @lynxcore.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
lynxcore.org
2a03:4000:8:4c9::1
 10
supported
lynxcore.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
55 s
lynxcore.org
37.221.193.109
 10
supported
lynxcore.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=lynxcore.org

Certificate chain
  • lynxcore.org
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • lynxcore.org
Alternative Names
  • lynxcore.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-07
Not valid after
2024-07-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6A:19:2F:78:A3:49:4A:E9:AA:5D:A5:F8:43:E3:18:76:C5:46:E9:B9:5B:78:94:26:5C:44:C4:9C:2B:29:B4:C7
SHA1
B4:8F:3F:1B:91:F9:6C:71:0F:4A:E4:82:96:8A:FF:45:CB:37:56:2C
X509v3 extensions
subjectKeyIdentifier
  • 6E:12:31:12:B4:D8:01:F8:66:03:D9:06:8B:88:F3:6D:7B:0E:E5:C2
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 : 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 : Apr 7 11:03:50.989 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:64:C4:59:BF:EE:7A:76:F5:B3:07:25:BC:
  • 88:43:85:4A:E7:2C:4F:B8:9E:2B:28:54:9F:09:BD:BA:
  • E9:87:C7:03:02:20:19:D6:9A:91:B2:C6:5A:55:79:D4:
  • 10:A7:7C:74:51:AA:B5:3F:AB:F8:D7:94:1B:05:C3:BC:
  • E9:00:6F:AC:6E:EE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Apr 7 11:03:51.111 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F3:96:8B:83:51:A3:EE:DD:29:EA:AB:
  • 2A:B3:70:4A:4A:B7:63:FD:43:F2:3D:25:21:08:65:27:
  • BB:A7:5E:6A:A1:02:21:00:FD:D2:54:D5:D7:78:54:98:
  • CF:58:C0:B9:54:7B:6C:6B:FC:02:62:21:5E:A7:6B:93:
  • 72:AA:2F:37:81:08:7D:74