SSL-Tools

SSL check results of iondynamics.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for iondynamics.net 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, 22 Jun 2024 10:00:58 +0000

The mailservers of iondynamics.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @iondynamics.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.iondynamics.net
2a01:4f8:200:7395::54
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
smtp.iondynamics.net
195.201.140.152
 10
supported
iondynamics.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=iondynamics.net

Certificate chain
  • iondynamics.net
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • iondynamics.net
Alternative Names
  • flux.iondynamics.net
  • imap.iondynamics.net
  • iondynamics.net
  • mail.iondynamics.net
  • postfixadmin.iondynamics.net
  • smtp.iondynamics.net
  • spam.iondynamics.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-23
Not valid after
2024-08-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
66:CF:B9:1F:D5:27:F7:E0:59:93:B8:D1:43:4E:CF:F3:B6:C8:DB:AC:92:85:03:0B:5D:D5:39:96:0E:83:6C:FB
SHA1
4C:9E:00:BC:A2:0A:26:D1:C1:2D:7B:0C:AA:66:4A:F8:5F:DD:EF:CE
X509v3 extensions
subjectKeyIdentifier
  • 09:E5:FE:FD:57:0F:DF:AF:12:8F:A6:36:34:4C:91:F7:88:9B:76:56
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 : 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 : May 23 07:15:43.300 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9E:B2:6A:D1:2B:B8:99:EB:5C:1A:62:
  • 88:57:48:98:0D:C3:F1:30:8A:76:CD:9A:8F:FA:ED:6A:
  • EE:D6:4B:49:DD:02:21:00:A7:BC:6E:48:1C:40:52:DB:
  • DC:43:3E:3B:BC:F4:5A:0D:04:5A:71:AA:15:40:6E:30:
  • 19:D5:53:89:27:23:54:8D
  • 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 : May 23 07:15:43.499 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:65:DF:8A:DD:A8:EA:44:F9:8D:4B:EB:D8:
  • 4B:64:BE:31:89:27:87:59:53:4F:36:8A:DC:8D:59:67:
  • 70:84:0D:68:02:21:00:E5:B4:10:CC:34:D0:75:E2:23:
  • E6:61:3D:B2:82:53:4D:31:00:1A:DC:4C:59:BF:5F:35:
  • 37:02:B3:3A:40:51:1C