SSL-Tools

SSL check results of mail.minkafighter.de

NEW You can also bulk check multiple servers.

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

The mailservers of mail.minkafighter.de can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.minkafighter.de
152.53.15.205
 -
supported
mail.minkafighter.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
mail.minkafighter.de
2a03:4000:6b:236:5826:f6ff:fe98:af91
 -
supported
mail.minkafighter.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 @mail.minkafighter.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.minkafighter.de

Certificate chain
  • mail.minkafighter.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.minkafighter.de
Alternative Names
  • mail.minkafighter.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-10
Not valid after
2024-06-08
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1B:16:D7:DC:A1:F9:4C:BC:BA:64:1B:CA:9F:A0:F5:84:BC:C9:CC:1E:25:D1:02:87:CE:81:DC:04:C8:E9:51:1D
SHA1
0F:1C:5D:AE:AE:39:CA:7B:35:19:B1:05:72:F1:FF:EA:72:96:98:61
X509v3 extensions
subjectKeyIdentifier
  • 46:78:8C:7A:14:AF:6B:53:CE:54:25:D1:58:B7:F4:E6:A1:60:0E:80
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 : 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 : Mar 10 17:52:33.507 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B0:33:B3:83:44:23:37:29:1F:79:8B:
  • 82:1F:C8:49:8A:4D:CA:2A:ED:29:34:F0:E4:A3:8F:9C:
  • B9:93:D6:55:46:02:21:00:E2:AF:E5:9D:66:63:70:0E:
  • 32:05:83:D9:07:42:1A:AC:98:67:32:7F:2D:56:79:94:
  • 17:49:8C:B3:00:54:E7:4E
  • 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 10 17:52:33.513 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:87:45:24:51:68:24:23:9D:29:5C:6A:
  • D6:28:3D:CD:D3:20:00:3F:FD:64:F8:DD:AE:2C:0C:1E:
  • 3B:02:CF:CA:AC:02:21:00:E5:39:75:10:AD:9C:87:92:
  • 48:CC:F6:6C:57:06:31:F8:4C:22:16:B8:34:88:14:DC:
  • 1C:3D:75:82:DB:37:88:12