SSL-Tools

SSL check results of mailmint.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mailmint.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, 24 Jan 2025 13:27:08 +0000

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

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

/mailservers/mailmint.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mailmint.de
91.229.245.113
Results incomplete
-
unsupported
not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s
mailmint.de
2a02:c206:3015:3765::1
 -
supported
mailmint.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
10 s

Outgoing Mails

We have not received any emails from a @mailmint.de address so far. Test mail delivery

Certificates

First seen at:

CN=mailmint.de

Certificate chain
  • mailmint.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mailmint.de
Alternative Names
  • mailmint.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-12
Not valid after
2025-04-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
65:C0:D5:D4:42:55:06:54:A3:65:71:F3:D0:1E:2D:ED:13:B6:00:1D:49:EE:37:83:F2:41:2C:96:52:1B:10:F3
SHA1
6A:B5:A1:51:AF:A6:AA:D6:47:89:0F:FC:E3:F8:9C:DE:C3:10:8D:3C
X509v3 extensions
subjectKeyIdentifier
  • 21:4B:8F:B1:69:7A:D6:E3:AD:CE:1A:97:26:E5:A9:00:01:35:32:1F
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 12 10:36:42.941 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:57:31:F6:44:AB:15:03:7A:EE:E4:3A:7B:
  • 46:9E:AE:7F:36:E8:32:43:EA:50:9D:84:C1:2E:87:FF:
  • DB:42:DB:2D:02:21:00:C0:56:1F:E1:37:20:A5:38:C0:
  • B5:C8:E0:BB:44:48:2C:03:4A:B9:DC:9E:CA:43:8B:08:
  • 78:FC:6D:E5:C4:FE:4F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Jan 12 10:36:43.131 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D8:E0:68:EE:05:75:4A:A8:AB:09:FD:
  • DE:00:C9:16:0D:57:00:BE:89:67:C7:55:25:6F:0B:E6:
  • A4:DC:09:27:D5:02:21:00:8D:AB:4A:74:9A:AA:D1:D0:
  • 70:92:C1:18:28:50:11:E5:99:BE:BE:FD:04:ED:49:2F:
  • 57:65:C4:71:2F:DB:44:5D

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mailmint.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
error
Debug
valid