SSL-Tools

SSL check results of iiq-check.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for iiq-check.de 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 Wed, 08 Apr 2026 08:32:34 +0000

The mailservers of iiq-check.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @iiq-check.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
postfix.iiq-check.cloud
2a01:4f8:c012:f545::1
 10
supported
postfix.iiq-check.cloud
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
postfix.iiq-check.cloud
116.203.6.108
 10
supported
postfix.iiq-check.cloud
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 @iiq-check.de address so far. Test mail delivery

Certificates

First seen at:

CN=postfix.iiq-check.cloud

Certificate chain
  • postfix.iiq-check.cloud
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • postfix.iiq-check.cloud
Alternative Names
  • postfix.iiq-check.cloud
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2026-03-21
Not valid after
2026-06-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
5B:4E:E1:79:53:B2:3F:BF:A2:17:52:49:7B:5B:7F:A1:E6:85:2D:6E:5B:33:94:1E:20:BB:FE:74:05:D7:38:F6
SHA1
CF:72:DF:7A:CB:26:7B:D9:37:8B:FC:33:00:3B:E7:79:77:D7:10:90
X509v3 extensions
subjectKeyIdentifier
  • ED:5F:20:0A:8C:B9:0E:32:41:8B:BB:34:48:A3:E4:49:17:43:B2:FD
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/79.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 71:7E:95:F3:C2:38:8A:6D:B1:E3:84:49:3D:31:E1:5A:
  • A9:62:08:76:2D:42:00:E0:05:0C:D0:67:B5:A6:61:E2
  • Timestamp : Mar 21 09:35:56.807 2026 GMT
  • Extensions: 00:00:05:00:0C:35:DC:2A
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3C:8B:74:B4:8F:C4:89:4A:2D:0F:A7:62:
  • 5C:C8:86:AE:D2:16:2A:89:1A:88:9C:35:78:56:C4:52:
  • 53:EC:2C:BD:02:21:00:92:11:A8:16:05:68:DC:CD:05:
  • B3:68:A8:D4:E0:CC:B9:33:F2:5D:66:39:16:E2:81:C5:
  • B8:69:DF:2A:EF:E8:A4
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 16:83:2D:AB:F0:A9:25:0F:0F:F0:3A:A5:45:FF:C8:BF:
  • C8:23:D0:87:4B:F6:04:29:27:F8:E7:1F:33:13:F5:FA
  • Timestamp : Mar 21 09:35:58.623 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5B:40:72:78:84:16:CD:3C:44:82:0A:5A:
  • 5A:8C:BC:24:64:26:2B:CA:12:70:02:FF:52:DA:51:2E:
  • D9:AA:6E:BC:02:20:5F:55:E4:F1:EB:06:A4:E2:84:D8:
  • 15:0D:55:E8:61:BA:D8:7E:A9:8C:62:F7:54:E1:BD:8A:
  • F5:B1:1A:94:23:E2