SSL-Tools

SSL check results of teamkoenig.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for teamkoenig.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 Fri, 30 Sep 2022 09:34:55 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
smx01.udag.de
62.146.106.51
 10
supported
smx00.udag.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
smx00.udag.de
62.146.106.50
 10
supported
smx00.udag.de
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 @teamkoenig.de address so far. Test mail delivery

Certificates

First seen at:

CN=smx00.udag.de

Certificate chain
  • smx00.udag.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)
  • smx00.udag.de
Alternative Names
  • smx00.udag.de
  • smx01.udag.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-09-25
Not valid after
2022-12-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E9:53:4E:B9:30:BA:24:18:65:24:75:47:54:10:22:65:96:10:89:B3:BB:08:69:FD:B7:FA:C7:0C:16:8E:5D:4B
SHA1
31:95:6C:F7:BC:31:1B:DF:3D:E7:CF:A2:21:A6:8D:FC:79:1E:54:18
X509v3 extensions
subjectKeyIdentifier
  • F2:7B:4F:E3:77:0A:61:9D:9A:DA:68:71:D9:5F:59:D4:9E:6D:49:EE
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 : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Sep 25 22:02:56.176 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CE:45:3D:CD:B0:9E:49:DE:2A:2B:0B:
  • 16:EB:67:94:0C:26:33:C7:A9:42:4F:59:EC:4A:E2:C2:
  • 22:44:73:05:60:02:20:65:B2:1B:D7:AA:63:E1:8B:DB:
  • 8A:F6:DB:ED:8C:85:12:1D:0C:40:17:C2:97:54:FA:91:
  • 55:C8:F9:8C:E0:A3:F4
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
  • 4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
  • Timestamp : Sep 25 22:02:56.686 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0B:95:E2:60:0C:2E:51:02:77:FA:05:39:
  • 35:B2:FB:84:09:D4:5A:10:1F:E4:D5:A0:64:45:D2:BB:
  • 16:07:67:49:02:21:00:FD:0B:3E:12:2E:99:3B:79:4A:
  • 06:F5:99:12:27:9C:6B:DF:22:9A:95:99:B0:64:A0:ED:
  • 8D:A6:7E:DA:AB:16:B3