SSL-Tools

SSL check results of mail.mgs-holding.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.mgs-holding.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

JSON Refresh

Report created Sat, 27 Apr 2024 05:53:44 +0000

The mailservers of mail.mgs-holding.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.mgs-holding.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mgs-holding.com
176.126.165.64
 -
supported
mgs-holding.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=mgs-holding.com

Certificate chain
  • mgs-holding.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)
  • mgs-holding.com
Alternative Names
  • *.mgs-holding.com
  • mgs-holding.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-26
Not valid after
2024-07-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
74:77:1C:04:2E:63:B2:3D:93:24:75:FA:28:E1:1F:9F:EF:6A:30:F9:2D:1F:9E:75:A3:4F:50:30:75:DB:CB:4C
SHA1
A6:83:2C:2C:28:C3:99:76:45:E1:3A:61:87:BE:2B:4A:5E:74:A8:69
X509v3 extensions
subjectKeyIdentifier
  • 70:62:55:13:27:B9:85:9D:9E:77:87:EE:D0:FB:D2:9B:E4:68:4D:5F
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 : Apr 26 13:23:15.425 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:39:C8:D0:F1:BF:BC:96:17:AA:02:59:AA:
  • 65:EE:1B:BF:11:77:36:B2:3B:33:01:90:C3:AE:98:EE:
  • BD:D9:76:46:02:21:00:A0:13:8F:C4:B7:24:E5:45:1D:
  • AB:B6:61:AD:A9:0F:6A:03:9F:AD:82:B6:6B:35:67:33:
  • D9:1A:5F:70:A9:DA:66
  • 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 26 13:23:15.618 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:20:C1:E7:96:29:52:DE:60:20:19:4F:42:
  • B5:E2:93:83:4D:3A:80:EB:8F:E2:DE:49:4F:C6:1F:59:
  • 50:9A:79:9E:02:20:76:D1:6F:DA:30:B4:DF:B1:D6:98:
  • 13:52:B5:66:29:4A:10:63:40:B4:38:7A:F4:60:DE:F2:
  • 0D:D6:77:03:5C:B7