SSL-Tools

SSL check results of mail.ability-style.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.ability-style.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 Thu, 01 Aug 2024 20:20:03 +0000

The mailservers of mail.ability-style.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.ability-style.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.ability-style.de
159.69.53.145
 -
supported
mail.ability-style.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.ability-style.de
2a01:4f8:c010:97bd::1
 -
supported
mail.ability-style.de
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 @mail.ability-style.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.ability-style.de

Certificate chain
  • mail.ability-style.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.ability-style.de
Alternative Names
  • mail.ability-style.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-07-31
Not valid after
2024-10-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
63:34:A2:8F:F9:98:27:1D:D0:C9:00:6F:C9:3D:E4:6B:A6:64:2A:C7:70:CB:08:AB:5F:DD:90:58:6E:7A:21:D4
SHA1
78:9F:DB:3E:57:18:A7:E4:9D:28:28:C5:EE:18:56:34:F4:AA:6D:8E
X509v3 extensions
subjectKeyIdentifier
  • 83:83:D8:D7:41:8B:68:55:9C:A1:C3:49:61:FE:29:5D:1C:2C:84:0C
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 : Jul 31 21:00:07.294 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C1:3A:AF:6F:13:C3:B1:CC:F0:5B:C6:
  • BA:AC:58:FA:62:41:22:79:5D:B6:B6:2E:67:3A:35:23:
  • 8C:85:32:45:2A:02:20:5E:CE:BD:BB:B0:0F:29:2E:BB:
  • C2:41:7A:BB:69:71:94:B3:45:E8:38:6A:A6:75:DA:4B:
  • D6:7F:96:D3:4F:E2:C1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Jul 31 21:00:07.288 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:57:34:2E:CD:A1:40:2F:DB:5E:19:18:BA:
  • 31:3E:59:C1:A4:D4:2D:32:EC:30:EE:6D:82:DD:6B:10:
  • 44:01:7B:4E:02:21:00:D1:A9:CA:8B:3D:BA:93:C3:12:
  • 6B:E1:F7:4D:92:50:6C:60:38:F4:ED:D9:71:D5:69:91:
  • 30:C2:65:E0:03:91:38
tlsfeature
  • status_request