SSL-Tools

SSL check results of krankenhaus-prignitz.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for krankenhaus-prignitz.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 Mon, 11 May 2026 11:51:27 +0000

We can not guarantee a secure connection to the mailservers of krankenhaus-prignitz.de!

Please contact the operator of krankenhaus-prignitz.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/krankenhaus-prignitz.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @krankenhaus-prignitz.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail2.krankenhaus-prignitz.de
80.150.121.244
 10
supported
mail2.krankenhaus-prignitz.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail3.krankenhaus-prignitz.de
80.150.121.245
Results incomplete
20 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
relay.rzone.de
81.169.145.96
Results incomplete
100
supported
relay.rzone.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @krankenhaus-prignitz.de address so far. Test mail delivery

Certificates

First seen at:

CN=relay.rzone.de,O=STRATO GmbH,ST=Berlin,C=DE

Certificate chain
Subject
Country (C)
  • DE
State (ST)
  • Berlin
Organization (O)
  • STRATO GmbH
Common Name (CN)
  • relay.rzone.de
Alternative Names
  • relay.rzone.de
  • www.relay.rzone.de
Issuer
Country (C)
  • GB
Organization (O)
  • Sectigo Limited
Common Name (CN)
  • Sectigo Public Server Authentication CA OV R36
validity period
Not valid before
2026-02-19
Not valid after
2027-02-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
51:76:4E:DB:A5:11:FE:D5:73:55:98:DE:3C:3A:C9:F9:74:F2:BA:0C:04:69:D1:EC:64:EE:18:45:15:17:90:63
SHA1
1F:2D:7D:51:33:D2:7F:C4:A0:77:F9:86:71:5F:63:13:B3:10:A0:C2
X509v3 extensions
authorityKeyIdentifier
  • keyid:E3:66:74:BB:70:68:8D:2C:5D:4E:0E:A6:4A:8F:9B:37:22:9C:82:92
subjectKeyIdentifier
  • 00:9B:39:0F:EB:E4:B3:8B:5F:44:91:AC:A2:7F:C1:E3:F0:1B:EE:80
certificatePolicies
  • Policy: 1.3.6.1.4.1.6449.1.2.1.3.4
  • CPS: https://sectigo.com/CPS
  • Policy: 2.23.140.1.2.2
crlDistributionPoints
  • Full Name:
  • URI:http://crl.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crl
authorityInfoAccess
  • CA Issuers - URI:http://crt.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crt
  • OCSP - URI:http://ocsp.sectigo.com
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 60:4C:9A:AF:7A:7F:77:5F:01:D4:06:FC:92:0D:C8:99:
  • EB:0B:1C:7D:F8:C9:52:1B:FA:FA:17:77:3B:97:8B:C9
  • Timestamp : Feb 19 14:03:42.163 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A4:06:DC:B9:C6:9E:56:59:2A:C8:C6:
  • 01:67:CA:DC:B1:E6:1C:3D:AB:D5:34:51:AE:B8:DE:2B:
  • A5:3A:22:9E:EB:02:20:45:77:C5:14:4E:FD:38:2F:B2:
  • 1C:63:27:CA:A7:D3:8E:44:2A:D5:59:67:14:71:53:82:
  • D5:93:B9:E2:D7:EB:40
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 8E:CA:47:0B:AC:DE:6A:F3:A2:06:B0:A4:7A:84:B7:46:
  • FE:1F:C6:BF:95:3E:25:E6:9B:4E:E4:02:48:F3:C6:E8
  • Timestamp : Feb 19 14:03:42.774 2026 GMT
  • Extensions: 00:00:05:00:02:DF:E4:16
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4A:45:43:FE:0B:87:A7:8F:E8:48:6A:D7:
  • 56:45:9D:C4:EF:FA:9F:57:70:FC:41:44:F0:45:BF:D1:
  • E4:42:F9:D5:02:21:00:DB:B2:33:AE:5E:AD:74:A5:AA:
  • 36:2D:B9:D8:29:AA:ED:BC:F7:79:70:38:BD:19:87:7C:
  • DB:E1:63:CA:E9:F8:67
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 59:6E:6C:33:86:94:B2:59:72:A2:56:C8:A0:E8:DD:90:
  • 4A:76:E8:08:3D:DA:87:3B:01:08:38:28:14:3C:EE:59
  • Timestamp : Feb 19 14:03:42.634 2026 GMT
  • Extensions: 00:00:05:00:00:2A:3B:FD
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:11:53:2E:57:BD:12:82:6D:D9:3A:50:05:
  • BC:AE:E8:B1:FB:B4:85:C1:5D:8A:5E:B1:43:F4:9F:3A:
  • C8:AF:36:74:02:20:12:29:48:8E:45:67:2E:00:FD:00:
  • E0:E2:02:AA:D8:C3:4E:40:43:66:48:0B:76:5B:B2:5A:
  • 8A:E8:11:2C:11:21
First seen at:

OU=IT,ST=Brandenburg,O=KKH Prignitz gGmbH,L=Perleberg,CN=mail2.krankenhaus-prignitz.de,C=DE

Certificate chain
Subject
Country (C)
  • DE
Common Name (CN)
  • mail2.krankenhaus-prignitz.de
Locality (L)
  • Perleberg
Organization (O)
  • KKH Prignitz gGmbH
State (ST)
  • Brandenburg
Organizational Unit (OU)
  • IT
Issuer

Certificate is self-signed.

validity period
Not valid before
2023-02-13
Not valid after
2033-02-10
Fingerprints
SHA256
1C:29:55:A4:27:CF:B9:B0:7E:68:F5:CA:19:FE:58:04:7D:79:6C:43:52:02:C8:22:1B:61:F1:9D:57:AC:FF:02
SHA1
4A:52:C4:FA:C0:AF:A9:5E:4D:32:7B:F6:01:E9:B0:68:A8:A0:9F:41