SSL check results of motforu.ddnss.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for motforu.ddnss.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

Report created Wed, 18 Dec 2024 01:31:20 +0000

We can not guarantee a secure connection to the mailservers of motforu.ddnss.de!

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

/mailservers/motforu.ddnss.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
motforu.ddnss.de
85.114.136.161
-
supported
mail.mc-p.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • SSLv3
12 s
motforu.ddnss.de
2001:4ba0:ffe6:1f::1
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.mc-p.de

Certificate chain
  • mail.mc-p.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mail.mc-p.de
Alternative Names
  • mail.mc-p.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-28
Not valid after
2025-01-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2F:A5:9F:AE:CE:B1:C3:1D:F2:93:7D:42:BB:0C:02:F4:61:07:01:1C:57:91:9A:EC:58:27:F0:A5:B9:E6:67:9C
SHA1
41:A5:91:4E:8D:7D:A7:3F:D1:52:49:8B:83:A4:F5:A7:14:80:76:B9
X509v3 extensions
subjectKeyIdentifier
  • C9:BC:B4:77:42:A7:DC:73:2E:1F:89:C3:06:3B:E8:FE:A6:ED:25:74
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 : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Oct 28 19:25:15.894 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CE:F3:2B:C8:FB:31:A6:4D:86:F3:AD:
  • BF:A8:E6:9F:06:61:29:73:A9:DE:0F:D4:F3:35:84:3D:
  • A7:A4:A7:E2:2B:02:20:46:42:7A:56:1B:38:EC:CD:23:
  • 1E:9D:95:03:52:85:A5:8C:09:D8:B6:E3:CC:BC:0F:9B:
  • 2D:C8:53:09:E9:B9:A7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Oct 28 19:25:17.906 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E1:96:71:81:1B:E3:01:0E:DA:19:3C:
  • 64:30:8A:6F:13:AC:2F:0A:EB:6D:33:31:80:1A:54:C4:
  • 0A:F5:2E:EF:7F:02:20:0E:3E:9D:AD:7D:41:F6:EA:90:
  • F9:C0:8D:5E:96:F0:0C:28:E3:D5:12:F2:49:59:2D:4F:
  • 2E:28:2C:E3:BE:F7:80