SSL check results of stackptr.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for stackptr.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 Fri, 11 Jun 2021 13:46:49 +0000

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

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

/mailservers/stackptr.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.stackptr.de
88.99.59.17
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mx01.stackptr.de
88.99.59.17
Results incomplete
20
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mx02.stackptr.de
95.217.34.116
30
supported
private-mail-for.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=private-mail-for.me

Certificate chain
  • private-mail-for.me
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • private-mail-for.me
Alternative Names
  • *.private-mail-for.me
  • private-mail-for.me
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-15
Not valid after
2021-06-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8D:61:39:F1:90:99:96:BA:FB:CB:09:24:61:A9:20:A9:93:C5:36:74:22:85:CA:8C:9E:3C:0F:A1:4A:57:35:3B
SHA1
5D:28:EC:1B:74:58:2F:9B:1F:EC:E6:6F:5D:8C:04:1B:9E:B8:77:0E
X509v3 extensions
subjectKeyIdentifier
  • 88:58:60:47:EE:9F:C9:89:60:7D:ED:F5:7D:06:EB:89:0A:A2:E7:BE
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Mar 15 23:12:44.219 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F1:CE:D9:2C:9B:22:4B:33:F0:EA:FA:
  • 05:F7:E4:04:99:BC:31:C3:2A:1B:02:49:C2:33:D0:65:
  • 3C:B4:73:41:E2:02:20:40:D8:74:00:09:61:C4:BF:B9:
  • 9E:BA:26:93:A6:58:8B:1B:DF:0F:64:25:49:4F:02:BB:
  • F8:41:0E:1C:9E:AD:60
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Mar 15 23:12:44.694 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:75:74:DC:1F:D0:3A:41:D9:48:C2:51:B8:
  • 9A:DE:81:BB:DB:88:93:5A:DE:EC:0F:E8:D0:33:05:00:
  • F7:A7:1D:59:02:21:00:D9:EE:0F:A5:73:25:E9:F6:8C:
  • 1F:0D:D5:6D:A8:50:41:CB:03:7E:3D:13:0F:A0:2E:A2:
  • BC:05:DE:D6:96:7A:7D