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

Report created Thu, 23 Jun 2022 18:17:38 +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:1c1c:14a6::1
10
supported
iondynamics.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 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
2022-05-30
Not valid after
2022-08-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A7:8B:DC:3F:E1:D2:DD:D7:7A:53:C8:95:53:A9:C1:90:DD:CA:4C:8E:DE:77:32:06:EB:30:B7:74:D4:A0:C2:47
SHA1
9B:42:1B:1D:8B:D5:64:A3:3A:2F:53:90:B5:C7:7B:91:C8:C8:97:1C
X509v3 extensions
subjectKeyIdentifier
  • 61:7A:F8:5C:D9:2D:60:32:64:B0:4F:76:E7:4A:7D:0D:C1:8B:69:EF
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
  • 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
  • Timestamp : May 30 15:05:14.605 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F3:A5:5D:8C:EB:D3:6E:EA:E5:E9:02:
  • CD:14:61:17:AC:39:0A:FB:A5:3C:23:9A:1D:96:13:8E:
  • 0D:2B:9B:EA:22:02:20:39:BB:17:74:63:13:5A:F2:3D:
  • DB:A6:A0:2A:07:74:49:B8:1F:42:3F:BB:38:33:AC:E1:
  • 24:5C:0A:3B:20:F0:17
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
  • EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
  • Timestamp : May 30 15:05:15.058 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BE:88:49:49:3B:DE:F8:42:1E:1C:31:
  • 71:7B:44:53:C2:A0:BB:D9:6D:64:BF:E9:E2:9D:13:AB:
  • 4A:2D:73:CF:DF:02:20:1B:6E:19:B2:79:3F:66:BF:88:
  • 8F:B6:DE:6B:53:F9:61:9D:15:41:49:AD:75:07:D9:86:
  • D3:89:61:3C:D5:D0:0F