SSL-Tools

SSL check results of damer.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for damer.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 Mar 2024 19:19:27 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.damer.de
2a02:247a:26d:d900::1
 10
supported
damer.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.damer.de
212.132.67.122
 10
supported
damer.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Host TLS Version & Cipher
mail.damer.de (81.169.132.233)
TLSv1.3 TLS_AES_256_GCM_SHA384
mail.damer.de (5.175.3.49)
Insecure - not encrypted!

Certificates

First seen at:

CN=damer.de

Certificate chain
  • damer.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)
  • damer.de
Alternative Names
  • *.damer.de
  • damer.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-23
Not valid after
2024-06-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
02:92:DD:F9:06:66:48:65:01:12:75:DD:8B:A1:99:26:5B:A6:96:5E:F2:08:96:A4:9A:26:91:11:83:F4:FF:1F
SHA1
1D:E9:9D:B1:F9:CB:AD:12:D3:5C:AE:76:8B:59:F8:29:D0:70:FC:69
X509v3 extensions
subjectKeyIdentifier
  • 9B:60:39:BD:6E:99:04:78:C3:6C:BA:9D:B8:44:9D:81:E1:F0:06:85
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 : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 23 11:37:21.774 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:80:EC:E1:38:43:EB:6F:C4:84:23:6B:
  • F2:8F:DB:90:DF:56:18:60:CE:0F:0B:8B:0F:52:92:C1:
  • D9:23:65:D3:75:02:20:57:5C:D0:E1:DA:D7:97:85:C2:
  • 74:93:97:1B:50:66:DB:75:5F:57:2F:4F:F6:87:64:62:
  • B3:BF:97:56:63:80:7F
  • 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 : Mar 23 11:37:23.760 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AB:8D:12:DB:D7:6D:3C:E5:2F:8E:66:
  • 00:1C:72:74:EE:6A:8B:CA:AA:69:49:83:85:C4:4C:DF:
  • 91:5C:16:97:13:02:20:27:5B:C7:67:D4:D4:75:F6:81:
  • 00:C9:CC:67:5D:4E:D3:10:A3:05:03:D2:C8:95:41:26:
  • C9:49:2E:FC:27:26:F2