SSL-Tools

SSL check results of mx1.grone-tec.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mx1.grone-tec.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 Mon, 20 Jan 2025 16:12:06 +0000

The mailservers of mx1.grone-tec.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mx1.grone-tec.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.grone-tec.de
62.112.51.21
 -
supported
mx1.grone-tec.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

We have not received any emails from a @mx1.grone-tec.de address so far. Test mail delivery

Certificates

First seen at:

CN=mx1.grone-tec.de

Certificate chain
  • mx1.grone-tec.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)
  • mx1.grone-tec.de
Alternative Names
  • autoconfig.fcc-hannover.de
  • autoconfig.grone-tec.de
  • autodiscover.fcc-hannover.de
  • autodiscover.grone-tec.de
  • mx1.grone-tec.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-18
Not valid after
2025-04-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6A:BB:9D:71:61:67:51:F5:11:31:5A:45:92:CD:88:84:D3:9C:22:1D:4D:63:FB:23:5F:CD:1F:7F:61:21:6F:50
SHA1
72:E2:CD:D6:3E:05:AD:97:5D:61:2A:89:AE:E3:D0:33:70:FD:A3:9F
X509v3 extensions
subjectKeyIdentifier
  • 54:B3:78:21:37:27:43:6E:5C:85:C9:16:B9:77:B0:F5:9D:1B:73:C9
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 : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Jan 18 18:09:27.566 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CA:01:1D:99:3C:42:F9:CE:42:C1:EE:
  • D1:0B:A8:7F:21:B9:5D:2A:07:81:5A:2B:B6:8C:EC:C7:
  • CD:A4:73:F0:C1:02:21:00:EC:4B:E1:16:23:28:1D:3B:
  • 13:38:DF:AC:02:32:D9:F5:5D:5E:28:CF:02:0C:82:32:
  • C8:4D:8B:EF:09:B7:1B:F5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Jan 18 18:09:27.584 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:61:6F:17:26:C9:91:02:83:C8:63:BE:22:
  • D6:B8:6C:EE:CF:5A:D6:72:71:A3:2E:39:5B:6E:FF:6E:
  • 43:9D:F8:72:02:21:00:A6:9B:0E:F6:89:43:A5:8D:68:
  • 89:DF:27:DC:65:BA:62:D9:A5:C2:50:3A:73:5D:00:28:
  • 54:22:A4:DC:CF:7F:BC