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, 23 Dec 2023 21:10:15 +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
5 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
4 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
    • 2048 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
2023-11-10
Not valid after
2024-02-08
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D5:09:A7:91:05:09:70:C5:B7:B7:76:DA:C4:A3:1F:A7:CB:DC:49:11:8E:2F:6A:16:AA:39:38:09:23:0E:51:28
SHA1
BD:DC:DB:A2:FC:B0:45:D7:DB:C0:06:91:37:A3:36:96:29:4E:15:26
X509v3 extensions
subjectKeyIdentifier
  • 95:B9:99:D4:B9:3C:24:EF:73:BC:2D:36:BF:2F:54:C0:E5:C9:77:41
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 : 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 : Nov 11 00:56:02.120 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FF:60:5E:7A:63:99:EC:AE:34:B3:3E:
  • 0A:FE:15:20:28:5D:26:76:45:AE:3F:DF:60:1E:4F:5B:
  • 2E:88:85:60:2C:02:21:00:FB:F9:56:C3:9A:31:3F:57:
  • F1:C3:6E:57:73:CE:A2:6A:54:AF:44:17:FE:44:80:16:
  • ED:0A:6F:C4:5B:F4:F8:00
  • 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 : Nov 11 00:56:02.208 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A8:7B:B2:72:44:F7:28:DC:70:FD:D5:
  • 03:FE:DF:B8:CE:6C:1F:F2:91:44:9A:20:25:25:E5:F2:
  • B6:6E:22:04:DE:02:20:49:2B:86:21:52:C3:9A:3C:6B:
  • A5:CC:09:C7:B7:98:97:85:F7:EA:A8:66:66:9C:A5:FF:
  • C2:AD:D1:51:75:50:A5

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