SSL check results of minktech.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for minktech.com 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

Report created Sat, 27 Apr 2024 13:28:54 +0000

The mailservers of minktech.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @minktech.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.minktech.com
2600:3c02::f03c:91ff:fef1:fe3
10
supported
mail.minktech.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mail.minktech.com
45.79.223.23
10
supported
mail.minktech.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.minktech.com

Certificate chain
  • mail.minktech.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mail.minktech.com
Alternative Names
  • mail.minktech.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-13
Not valid after
2024-07-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2D:29:AD:73:B5:BB:91:F6:D0:7E:16:B7:1D:F3:5E:4B:1B:83:17:82:A5:1A:2D:62:1B:59:AD:4E:FE:46:7A:05
SHA1
49:10:BB:EA:77:24:18:BC:CA:10:3E:5B:2A:44:DE:4F:00:12:1B:54
X509v3 extensions
subjectKeyIdentifier
  • 5E:52:FD:D8:16:B5:EA:96:C3:A8:BA:B4:5F:D7:A8:DF:42:9E:32:B2
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 : 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 : Apr 13 04:08:02.899 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CA:C0:D8:BB:84:28:E9:AD:BE:59:3E:
  • C4:FC:5F:EF:86:B2:DA:C2:A5:C5:3A:CD:56:63:96:DC:
  • C5:DB:BB:07:CD:02:21:00:84:61:E2:2D:DD:A5:43:7D:
  • 97:5D:59:D9:5D:26:D3:B2:2B:40:AF:16:9B:73:71:20:
  • 5F:EF:6C:3E:0C:BF:FB:26
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Apr 13 04:08:03.112 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:96:0F:56:38:34:31:D0:15:91:EB:88:
  • 41:97:8F:E2:21:63:0F:76:AF:71:1E:04:31:2E:F3:74:
  • 2B:62:36:4F:BA:02:20:17:A0:DE:6B:6F:24:B8:C0:7E:
  • CB:D3:08:91:57:AF:31:36:73:2B:30:CE:13:94:F6:7C:
  • B5:52:C7:AC:5F:DE:46