SSL-Tools

SSL check results of itqs.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for itqs.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, 27 Mar 2024 20:49:25 +0000

The mailservers of itqs.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @itqs.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.itqs.de
81.169.135.113
 10
supported
webserver.itqs.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
www.itqs.de
81.169.135.113
 50
supported
webserver.itqs.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=webserver.itqs.de

Certificate chain
  • webserver.itqs.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • webserver.itqs.de
Alternative Names
  • ftp.itqs.de
  • imap.itqs.de
  • itqs.de
  • mail.itqs.de
  • smtp.itqs.de
  • tgui.itqs.de
  • webserver.itqs.de
  • www.itqs.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-14
Not valid after
2024-05-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8E:B7:28:31:A7:FF:04:B2:5E:26:20:BB:33:D3:99:67:BD:AA:38:BD:25:3D:3C:83:DD:A2:8C:C7:26:B6:A6:0D
SHA1
97:32:6B:96:96:81:49:67:CF:A9:EF:03:1D:70:BD:B0:FF:21:C4:80
X509v3 extensions
subjectKeyIdentifier
  • 74:25:F2:52:7B:00:4A:6F:74:28:FF:61:1F:82:DC:2A:DB:97:48:C0
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Feb 14 23:47:09.038 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:36:33:65:73:39:99:27:8B:C2:54:85:55:
  • DE:B8:DF:32:1D:25:FA:07:DA:0C:B3:DB:2D:21:30:C7:
  • AD:82:23:66:02:21:00:94:78:06:E9:76:42:C7:41:66:
  • E2:A2:CF:AB:4D:7F:60:CC:76:A7:42:20:36:5B:6B:A0:
  • 2E:84:68:01:C5:2C:62
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Feb 14 23:47:09.611 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9A:53:C0:6D:4A:61:04:59:D4:96:74:
  • E2:E0:CE:B7:AD:F6:5F:C5:4E:5C:E6:C9:7B:43:C1:38:
  • 32:C3:1D:2E:D7:02:21:00:D9:CE:8B:66:BA:F2:A7:70:
  • A6:E5:8A:6A:C2:94:DF:B7:43:9F:C9:01:BC:DB:E3:F4:
  • B2:5D:69:59:36:B7:E7:6B