SSL-Tools

SSL check results of mhnnet.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mhnnet.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:06:29 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
server.mhnnet.de
2a03:4000:5a:d9b::1
 10
supported
server.mhnnet.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
server.mhnnet.de
202.61.202.193
 10
supported
server.mhnnet.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=server.mhnnet.de

Certificate chain
  • server.mhnnet.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)
  • server.mhnnet.de
Alternative Names
  • server.mhnnet.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
75:BD:11:23:C6:DE:36:F5:13:FD:6A:1D:4D:B2:AE:7A:F1:33:4A:AA:0A:7C:82:4A:2E:06:9C:74:B4:AB:46:F4
SHA1
11:98:91:E6:B0:9E:7E:BC:12:55:3A:F5:65:16:70:0C:F3:9B:A1:4D
X509v3 extensions
subjectKeyIdentifier
  • 68:C1:F7:57:E1:6C:97:FE:BB:ED:57:9D:07:78:3F:88:8F:C3:61:6E
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 : 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 : Mar 23 18:36:53.530 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3F:10:3B:E6:78:F3:6E:FE:8E:1F:22:7A:
  • AE:80:5D:68:8D:EF:7A:B5:56:2A:65:2D:BD:6F:FC:BF:
  • F6:99:F9:92:02:20:45:71:C8:C6:5B:DC:0B:3D:6D:1A:
  • 15:36:B2:83:5D:36:60:7D:BA:93:7F:BA:F4:84:9F:44:
  • 05:82:A5:6C:BB:C9
  • 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 18:36:53.608 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DF:AF:97:C2:8F:CC:0F:C3:69:7D:66:
  • 51:FB:34:35:BA:2A:06:99:E7:22:5E:82:07:E2:3D:B2:
  • 96:AB:2E:35:65:02:20:76:C8:0A:07:39:EB:0D:F5:3D:
  • 69:C0:A1:54:14:E0:FC:34:BD:AF:6E:D1:EC:11:C3:2F:
  • 9A:46:B8:2D:1B:EA:92

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.server.mhnnet.de
  • PKIX-TA: CA Constraint
  • Use subject public key
  • SHA-256 Hash
valid
valid