SSL-Tools

SSL check results of elbe-land.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for elbe-land.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 Thu, 05 Sep 2024 09:19:06 +0000

The mailservers of elbe-land.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @elbe-land.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
the.ntpwr.de
2a01:4f8:130:5365:88:198:86:130
 10
supported
ntpwr.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
the.ntpwr.de
88.198.86.130
 10
supported
ntpwr.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 @elbe-land.de address so far. Test mail delivery

Certificates

First seen at:

CN=ntpwr.de

Certificate chain
  • ntpwr.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • ntpwr.de
Alternative Names
  • nsg.ntpwr.de
  • ntpwr.de
  • the.ntpwr.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-07-24
Not valid after
2024-10-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
4E:97:6D:CF:B7:08:52:0C:B0:5C:1E:30:84:60:DA:AA:C6:20:CF:D5:A8:24:DA:98:B4:83:B2:DE:98:FA:3F:58
SHA1
B3:B7:F0:E1:1F:C0:F4:3C:FE:3F:8C:BD:4A:20:6A:B1:F1:2D:3D:C8
X509v3 extensions
subjectKeyIdentifier
  • 07:B7:ED:C8:0F:64:FB:2F:C8:37:B3:3B:8F:15:A6:2D:AA:10:E5:7C
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Jul 24 10:00:05.576 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5F:2F:DD:66:23:D4:58:02:9B:CB:F6:EB:
  • 41:1A:A3:51:4A:C9:15:0C:43:D2:55:C9:F4:1E:B9:80:
  • CF:35:EB:8C:02:20:36:50:6E:95:01:BA:A7:F6:A7:16:
  • 5D:D8:05:3F:25:01:60:82:F5:34:4D:B3:5F:19:B5:12:
  • 87:A2:1B:C7:9B:70
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Jul 24 10:00:05.526 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F8:C8:2F:E2:9F:FB:7E:25:93:AD:D2:
  • F5:2E:1C:70:BE:42:66:10:71:78:5B:93:6F:91:4C:02:
  • 2F:7E:65:AC:17:02:21:00:C0:C9:85:3F:C2:4B:44:CE:
  • 6A:80:75:51:E5:CA:E2:77:24:CE:D5:63:81:1E:F7:88:
  • 35:F5:83:59:42:87:5C:C7