SSL-Tools

SSL check results of m.stefan.wf

NEW You can also bulk check multiple servers.

Discover if the mail servers for m.stefan.wf 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, 20 Jan 2022 17:02:19 +0000

The mailservers of m.stefan.wf can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @m.stefan.wf addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
m.stefan.wf
159.69.9.5
 -
supported
m.stefan.wf
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
m.stefan.wf
2a01:4f8:c2c:7c3c::
 -
supported
m.stefan.wf
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 @m.stefan.wf address so far. Test mail delivery

Certificates

First seen at:

CN=m.stefan.wf

Certificate chain
  • m.stefan.wf
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • m.stefan.wf
Alternative Names
  • m.stefan.wf
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-01-20
Not valid after
2022-04-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
57:63:14:7E:00:4E:A9:89:B5:C4:D0:9F:03:93:C4:F8:15:64:47:4E:AF:86:44:3C:79:3A:2B:8D:2D:57:FB:0C
SHA1
AB:CA:47:45:FA:CF:EC:5F:99:2A:79:0B:CA:02:23:E1:1A:21:25:2E
X509v3 extensions
subjectKeyIdentifier
  • 97:5E:05:58:6D:1B:F5:CE:2A:AA:6A:EE:19:FA:F4:E0:38:64:BE:C5
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 : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
  • 4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
  • Timestamp : Jan 20 16:50:54.180 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9F:7E:A5:3E:1B:4E:2D:41:1A:1A:12:
  • 93:68:7A:81:E4:DF:B4:42:B1:CC:DD:E7:C2:BE:1B:B6:
  • 33:72:E7:43:32:02:21:00:E1:D4:06:A3:17:10:11:AC:
  • 8B:EA:63:5C:0D:93:B4:93:2E:C7:EF:D2:93:03:12:0F:
  • 20:8D:ED:5D:10:57:14:A8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
  • 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
  • Timestamp : Jan 20 16:50:54.212 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:90:A8:21:14:D3:90:8E:0E:72:71:A4:
  • 1F:A0:36:58:2D:26:FF:9A:A5:3D:4D:C0:67:50:4B:46:
  • A7:08:25:0C:49:02:21:00:94:D0:E1:4B:E6:32:65:87:
  • 18:BA:65:0D:DD:E1:AF:EA:FF:DE:20:C3:15:A0:EE:5D:
  • 9A:2B:95:6A:8D:75:66:72