SSL-Tools

SSL check results of gunger.xyz

NEW You can also bulk check multiple servers.

Discover if the mail servers for gunger.xyz 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, 12 Jan 2021 04:06:28 +0000

We can not guarantee a secure connection to the mailservers of gunger.xyz!

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

/mailservers/gunger.xyz

Servers

Incoming Mails

These servers are responsible for incoming mails to @gunger.xyz addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.gunger.xyz
85.227.130.106
 10
supported
gunger.xyz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mx2.gunger.xyz
195.178.166.247
Results incomplete
50 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=gunger.xyz

Certificate chain
  • gunger.xyz
    • remaining
    • 3072 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • gunger.xyz
Alternative Names
  • gunger.xyz
  • mx1.gunger.xyz
  • view.gunger.xyz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2020-12-27
Not valid after
2021-03-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9A:A5:6B:03:2A:D7:C2:89:A3:98:5B:AF:80:C5:C7:40:C1:0E:A0:A2:CB:25:9C:5B:C3:AC:80:0C:7B:FF:9B:AC
SHA1
23:7E:8F:72:BB:18:68:D6:01:E9:D7:DF:FD:3F:20:F6:CC:EF:83:07
X509v3 extensions
subjectKeyIdentifier
  • BA:AD:D9:E5:AE:FB:C2:86:88:E1:65:BF:5E:43:D6:79:75:BB:FA:F8
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 : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Dec 27 02:16:13.459 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F6:67:94:BA:B1:FB:AE:3C:AF:AD:A4:
  • 4B:DD:EE:1C:E1:12:64:49:CC:03:79:48:89:D6:97:0C:
  • BB:8D:49:05:89:02:21:00:CC:4A:89:80:F9:49:8E:8F:
  • 99:F0:DB:B0:A1:BF:1F:A0:62:A4:9F:1B:14:88:50:6A:
  • BB:C3:67:5B:74:2C:3B:DA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Dec 27 02:16:13.655 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9F:76:45:4E:46:AC:8A:1B:B8:5B:65:
  • E3:42:1C:48:3A:2D:8B:E6:11:C0:BD:43:4D:DF:E8:12:
  • AF:2D:93:0C:41:02:20:3E:08:DC:AA:A9:27:C3:EE:63:
  • 84:21:E9:28:A5:4F:70:50:56:D7:4E:B1:48:5A:07:69:
  • A8:0B:98:5F:F6:8F:37