SSL-Tools

SSL check results of awesome-it.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for awesome-it.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 Sat, 08 Jun 2024 05:01:42 +0000

The mailservers of awesome-it.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @awesome-it.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
k8s-prod-w-1.awesome-it.de
2a01:4f8:222:d9f::2
 10
supported
awesome-it.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
k8s-prod-w-1.awesome-it.de
213.239.205.118
 10
supported
awesome-it.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @awesome-it.de sender addresses. Test mail delivery

Host TLS Version & Cipher
k8s-prod-w-1.awesome-it.de (213.239.205.118)
Insecure - not encrypted!

Certificates

First seen at:

CN=awesome-it.de

Certificate chain
  • awesome-it.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)
  • awesome-it.de
Alternative Names
  • *.awesome-it.de
  • awesome-it.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-31
Not valid after
2024-08-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2C:16:4A:2E:E7:2A:9B:E8:B2:21:38:85:2A:7A:9D:99:DF:3E:12:D7:D5:4F:7E:90:08:09:B9:AD:E6:A4:20:51
SHA1
0D:A3:83:48:BE:38:BC:24:3D:B4:63:C8:76:3F:9B:30:A7:64:DA:4F
X509v3 extensions
subjectKeyIdentifier
  • FF:77:9B:16:B1:A2:AC:31:F7:A1:EC:A8:64:9F:DF:E9:5E:3E:26:51
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : May 31 10:22:15.276 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CB:17:97:1E:35:CA:A4:57:A1:B0:82:
  • 70:5F:AE:62:B6:5D:AB:1F:92:47:8B:02:FE:A6:31:EB:
  • 1B:9E:25:F6:2B:02:21:00:C2:64:61:CA:AC:DD:AA:F8:
  • 50:13:9F:8D:4D:BE:E1:25:43:3C:79:9B:A7:7D:22:35:
  • 48:78:4B:3F:6A:9C:3D:84
  • 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 : May 31 10:22:15.311 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C6:9F:30:E0:CF:0D:16:28:AD:83:4C:
  • 8D:9F:9E:BB:C6:5E:59:81:51:B1:F0:58:30:7D:69:EC:
  • B3:AA:98:12:76:02:20:7E:5B:41:C2:85:7A:FC:01:21:
  • 79:78:B2:82:36:F6:02:80:BB:B2:D6:C7:E0:99:6A:82:
  • 44:0D:C7:DE:BC:C0:E7

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.k8s-prod-w-1.awesome-it.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid