SSL-Tools

SSL check results of gginterserv.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for gginterserv.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 Tue, 18 May 2021 06:31:12 +0000

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

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

/mailservers/gginterserv.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
svr6.gginterserv.de
2a01:238:42b6:3700:29af:931b:18ce:cb8f
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
svr6.gginterserv.de
81.169.202.1
 10
supported
gginterserv.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=gginterserv.de

Certificate chain
  • gginterserv.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • gginterserv.de
Alternative Names
  • gginterserv.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-05-02
Not valid after
2021-07-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
05:72:31:67:52:23:82:9D:59:56:69:AD:2F:EA:EB:01:9A:CB:83:A8:9A:26:73:2C:71:30:BB:F7:7D:62:7A:26
SHA1
46:66:39:2A:E0:DB:69:78:33:8C:15:3C:8A:AB:2D:7C:4C:DF:5E:FC
X509v3 extensions
subjectKeyIdentifier
  • 3B:A2:D4:EA:34:6C:56:0E:73:24:23:2F:72:D7:E7:6D:33:95:F8:DB
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : May 2 23:43:40.108 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:98:F2:41:C3:5F:29:B2:8F:B2:88:F5:
  • 51:3C:2C:8D:AB:07:D7:9A:15:06:F5:74:89:F2:51:D2:
  • 32:D2:FB:BB:CB:02:21:00:EF:46:90:E2:FE:77:02:9E:
  • D3:75:C7:17:F3:59:6F:A2:A6:9A:93:3F:47:FD:DD:86:
  • CA:96:85:5B:0A:5C:92:B8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : May 2 23:43:40.197 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:80:8C:5F:13:CC:F0:26:BB:B4:E6:E5:
  • 69:2B:DD:24:1C:21:04:47:92:43:93:74:E8:82:5A:41:
  • FB:7A:66:3D:31:02:21:00:94:B4:DE:C2:F0:34:42:4B:
  • 07:00:46:C6:B9:4E:EA:50:FD:AB:0A:4D:02:0D:38:97:
  • 4C:64:E4:6F:D8:F5:35:FC