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 Tue, 23 Apr 2024 07:17:36 +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
2 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-03-24
Not valid after
2024-06-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
09:25:00:42:77:B5:83:6F:69:34:19:E0:30:EA:47:AC:CE:6D:9F:AA:E0:E2:05:D8:14:8D:82:9A:FF:48:03:30
SHA1
B2:CB:B6:19:0D:A3:7C:F5:34:BE:8A:67:05:C5:6B:8F:07:EC:BB:5A
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 : Mar 24 06:55:26.762 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8D:CD:7E:FC:09:8C:02:44:EA:37:02:
  • 01:C8:BC:A1:B0:C0:3D:D2:C2:4A:C1:CC:B4:A7:B7:AB:
  • E7:CE:6C:97:03:02:21:00:80:FC:45:6D:E1:A0:79:79:
  • B0:29:92:2E:85:62:C0:A3:6E:AD:3E:0D:31:35:E1:8E:
  • AD:1B:D7:DB:E3:3C:5F:00
  • 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 : Mar 24 06:55:26.806 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9D:56:71:B8:5E:7B:42:5B:A5:F7:BD:
  • C1:9E:BE:EF:CD:4A:39:EA:E1:52:62:43:4D:FC:FA:1F:
  • 0D:89:09:3F:C9:02:21:00:99:A9:EF:88:D4:EE:17:C8:
  • C9:70:A8:8D:0E:1D:77:C8:03:39:C6:D4:90:FB:36:A0:
  • 89:D1:BE:D2:D4:0E:C3:81