SSL check results of dreschner.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for dreschner.net 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 Thu, 25 Apr 2024 03:16:10 +0000

The mailservers of dreschner.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @dreschner.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.dreschner.net
2a02:c206:3002:9996::1
10
supported
dreschner.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.dreschner.net
213.199.61.29
10
supported
dreschner.net
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 @dreschner.net address so far. Test mail delivery

Certificates

First seen at:

CN=dreschner.net

Certificate chain
  • dreschner.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • dreschner.net
Alternative Names
  • *.dreschner.net
  • dreschner.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-25
Not valid after
2024-07-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2A:81:C6:92:3E:F8:00:9B:DE:D8:9B:6D:40:9C:CC:41:38:FA:A1:D6:FA:06:E0:CF:DD:CA:C4:1E:8E:09:06:6C
SHA1
40:F6:20:DA:2D:B3:C4:D8:45:13:8B:99:D9:15:88:36:52:A4:D1:41
X509v3 extensions
subjectKeyIdentifier
  • D9:59:6E:6E:78:7F:DF:B8:94:54:68:8A:5B:E9:6D:23:9D:33:F7:F6
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 : Apr 25 03:15:54.859 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9C:54:DE:C5:D2:4D:04:E9:9C:A3:F0:
  • AB:9F:FF:D1:80:8A:8C:17:1D:F8:18:25:DC:9E:D2:96:
  • 22:F9:23:B6:92:02:20:44:69:C5:74:CE:08:5C:00:AB:
  • 2C:37:FD:5B:9C:6E:C9:86:F4:F1:74:78:24:79:3E:DD:
  • 53:CE:90:44:91:B5:C1
  • 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 : Apr 25 03:15:54.854 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E3:17:AB:33:0B:07:BC:28:F5:4F:47:
  • 71:2C:A6:F3:2F:9D:2C:05:BF:DC:D9:78:8B:10:53:38:
  • 73:B1:F9:27:6F:02:21:00:BA:34:3A:1F:2D:64:A9:E8:
  • 6D:FA:6B:18:5E:8C:57:E9:06:74:E8:F4:EF:0D:F9:F6:
  • 67:82:B4:1D:75:AA:98:5E