SSL-Tools

SSL check results of aloof.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for aloof.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 Wed, 24 Apr 2024 15:22:27 +0000

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

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

/mailservers/aloof.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.aloof.de
2a03:4000:6:f0:e:a:1:2
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
2 s
mx.aloof.de
46.38.231.127
 10
supported
mx.aloof.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 @aloof.de address so far. Test mail delivery

Certificates

First seen at:

CN=mx.aloof.de

Certificate chain
  • mx.aloof.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)
  • mx.aloof.de
Alternative Names
  • mx.aloof.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-24
Not valid after
2024-06-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C0:C9:3D:30:07:D9:3E:74:AE:48:1C:46:1C:F8:B8:6F:34:D9:34:C8:BA:0E:37:9D:77:3B:54:94:A1:A4:05:2D
SHA1
63:B3:54:66:EE:06:7B:C4:A2:C3:30:CB:4E:C3:0D:15:E1:93:17:A5
X509v3 extensions
subjectKeyIdentifier
  • CF:01:ED:39:21:4A:6D:C3:E0:EF:B6:BF:DD:40:1C:30:86:8B:EE:86
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 25 00:35:15.682 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:76:46:5F:40:76:04:0C:91:73:6A:FE:91:
  • 98:58:01:E3:DF:CA:0F:B5:BF:D4:36:FA:30:65:36:9D:
  • 8C:CE:05:AC:02:20:59:E4:F1:66:DC:DA:27:79:E3:5C:
  • 20:75:6A:45:1A:50:16:38:F0:75:F3:F0:9E:B5:99:F6:
  • 08:03:89:1E:5F:88
  • 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 : Mar 25 00:35:15.671 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C2:FB:1E:B4:C7:F5:3E:AE:00:00:77:
  • CE:90:28:4C:45:65:6D:03:A2:45:62:31:B7:E1:4A:D5:
  • 38:74:02:EA:BB:02:21:00:ED:4F:1B:CB:3D:6A:6C:ED:
  • 5E:FD:BF:64:E3:B3:C8:F0:72:6D:53:5D:8C:F7:3F:57:
  • 14:4D:1B:B9:F6:3B:DF:ED