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 Fri, 23 Feb 2024 08:27:31 +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-01-24
Not valid after
2024-04-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AD:02:56:19:E9:29:DF:4B:81:0C:55:B2:6E:87:B1:71:72:46:E9:BC:94:BD:3E:DE:5B:7C:E5:E3:DB:00:C5:C2
SHA1
F5:C8:39:0F:A6:BD:54:8D:5E:3F:BB:20:E3:B0:1C:47:22:67:BD:F1
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
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 : Jan 24 06:55:12.885 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B4:5A:04:03:12:D5:DE:72:52:37:4C:
  • D5:9D:BD:0A:D2:F9:A4:0D:0F:28:B0:DE:03:8D:80:83:
  • A8:70:50:8A:2E:02:21:00:B9:E7:75:08:36:C0:23:71:
  • 32:50:B3:B7:07:A6:9C:0A:27:FE:0C:B1:C9:93:6D:D6:
  • CF:FC:ED:7C:E2:81:19:EF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Jan 24 06:55:12.805 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:75:92:F7:21:50:17:A1:F4:0C:9C:63:2D:
  • 1D:84:76:40:F6:A2:7E:73:AB:2D:CB:07:A9:4B:BB:93:
  • 03:D4:24:E6:02:21:00:AD:B4:47:7C:E1:30:A1:2A:4E:
  • E5:2B:B1:A3:0D:F6:24:CE:83:BA:8A:B4:ED:1B:B1:C1:
  • 2F:3A:67:60:30:67:24