SSL-Tools

SSL check results of de3.1ne.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for de3.1ne.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

JSON Refresh

Report created Mon, 25 Jan 2021 17:54:40 +0000

The mailservers of de3.1ne.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @de3.1ne.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
de3.1ne.de
95.216.32.24
 -
supported
de3.1ne.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
de3.1ne.de
2a01:4f9:2a:2067::2
 -
supported
de3.1ne.de
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 @de3.1ne.de address so far. Test mail delivery

Certificates

First seen at:

CN=de3.1ne.de

Certificate chain
  • de3.1ne.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • de3.1ne.de
Alternative Names
  • de3.1ne.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-25
Not valid after
2021-04-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F4:76:5D:AF:45:E0:08:C7:81:3E:9A:C8:F2:6F:DA:0C:1F:9D:51:2A:0B:2E:5E:C2:23:CB:50:82:29:EA:5E:18
SHA1
1A:D5:B0:F4:71:EC:AE:CE:F8:6E:B2:36:48:D3:E2:9F:BE:EB:C6:BA
X509v3 extensions
subjectKeyIdentifier
  • F2:26:16:29:0A:9D:8B:A2:7E:1B:69:E6:1F:CC:0A:AE:8A:FF:E4:F9
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Jan 25 02:02:52.448 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E7:11:51:99:F9:C4:00:58:45:DA:7E:
  • F3:93:31:0C:30:D9:2F:39:54:07:F1:F3:ED:25:8C:D4:
  • BB:39:EA:4B:36:02:20:45:D1:66:16:FD:EC:30:36:5E:
  • 36:62:4A:6E:84:D6:42:9D:34:86:17:E2:DE:C1:C6:87:
  • 84:4A:EA:17:81:1D:61
  • 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 : Jan 25 02:02:52.478 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:21:00:F6:1A:73:DF:46:D3:22:75:C4:C7:EC:
  • 10:B8:73:7F:68:33:76:3A:70:F6:89:9C:22:EA:39:72:
  • F4:8C:8B:2B:84:02:1F:24:D3:FF:1E:CB:73:23:04:D8:
  • DD:37:AF:A0:DF:BA:13:BF:71:D0:FB:44:FE:14:66:3B:
  • B4:08:E6:85:CC:02