SSL-Tools

SSL check results of wiesenfest.world

NEW You can also bulk check multiple servers.

Discover if the mail servers for wiesenfest.world 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 Fri, 26 Apr 2024 20:03:39 +0000

The mailservers of wiesenfest.world can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @wiesenfest.world addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.wholewildworld.de
2a01:239:25d:a100::1
 10
supported
mail.wholewildworld.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.wholewildworld.de
194.164.193.189
 10
supported
mail.wholewildworld.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.wholewildworld.de

Certificate chain
  • mail.wholewildworld.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.wholewildworld.de
Alternative Names
  • mail.wholewildworld.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-31
Not valid after
2024-06-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E0:B5:85:2E:B5:85:5F:61:2E:A7:AF:0D:B3:D4:72:6A:1D:26:33:16:1B:6E:5F:55:69:9F:01:E8:F8:12:13:91
SHA1
BB:B3:67:E0:E6:19:1C:E5:63:0B:AA:59:50:56:2A:B1:73:13:23:49
X509v3 extensions
subjectKeyIdentifier
  • 75:A6:F9:FA:C2:BE:5B:56:DD:FD:A4:D8:F6:E7:80:2B:D1:E2:70:E1
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Mar 31 20:39:15.899 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:62:EB:8F:7E:23:B2:F4:39:99:6B:46:BA:
  • 9E:7B:E7:1E:B9:CF:65:0A:92:59:BA:51:88:69:DB:CC:
  • F7:C9:13:17:02:20:29:24:87:F7:01:E3:99:8D:0D:CF:
  • 66:B1:5B:9D:6E:07:9D:02:5A:2B:71:4B:31:A1:A5:7E:
  • F3:FB:DD:6D:D1:21
  • 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 31 20:39:15.919 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:30:2D:7B:23:4D:AD:44:16:61:5E:4C:C7:
  • 4C:F9:6D:56:4B:55:63:C5:8D:4B:F6:32:F4:38:A7:93:
  • 66:AC:33:88:02:21:00:90:7A:73:AD:D6:FA:1C:02:22:
  • DC:C3:4D:E1:34:1C:87:7A:F0:F8:3F:72:4D:FB:FE:AD:
  • E5:D9:56:31:F9:38:CB