SSL-Tools

SSL check results of gt50.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for gt50.org 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, 07 Sep 2021 21:22:47 +0000

We can not guarantee a secure connection to the mailservers of gt50.org!

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

/mailservers/gt50.org

Servers

Incoming Mails

These servers are responsible for incoming mails to @gt50.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.gt50.org
5.88.224.144
 10
supported
*.gt50.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s
mail2.gt50.org
46.101.43.10
Results incomplete
60
supported
not checked
DANE
missing
PFS
not checked
Heartbleed
not vulnerable
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.gt50.org

Certificate chain
  • *.gt50.org
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Unknown Authority
      Sectigo RSA Domain Validation Secure Server CA
Subject
Common Name (CN)
  • *.gt50.org
Alternative Names
  • *.gt50.org
  • gt50.org
Issuer
Country (C)
  • GB
State (ST)
  • Greater Manchester
Locality (L)
  • Salford
Organization (O)
  • Sectigo Limited
Common Name (CN)
  • Sectigo RSA Domain Validation Secure Server CA
validity period
Not valid before
2021-01-04
Not valid after
2022-02-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EF:4F:42:93:82:D5:ED:4C:D2:5B:CE:55:DD:5F:18:76:BC:7D:22:7D:2D:9E:DE:55:5C:03:F8:89:96:F1:F6:BC
SHA1
BC:D3:73:98:3E:61:6E:FE:A4:98:73:7B:43:C9:B7:B0:84:61:6A:61
X509v3 extensions
authorityKeyIdentifier
  • keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
subjectKeyIdentifier
  • DF:CE:F9:CB:35:90:30:7F:0B:A3:1D:68:1E:F1:B9:6B:2D:11:6C:3E
certificatePolicies
  • Policy: 1.3.6.1.4.1.6449.1.2.2.7
  • CPS: https://sectigo.com/CPS
  • Policy: 2.23.140.1.2.1
authorityInfoAccess
  • CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
  • OCSP - URI:http://ocsp.sectigo.com
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
  • 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
  • Timestamp : Jan 4 15:46:13.228 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2A:F8:1D:70:51:66:58:81:D8:3E:2D:C0:
  • C4:AC:0C:71:68:DE:A7:C3:42:92:7B:30:52:AB:8C:FB:
  • 7F:5D:6F:74:02:21:00:A2:C4:70:9A:C1:E6:DD:84:C8:
  • 4D:EF:C4:6B:15:27:7E:AC:24:1A:B7:46:44:68:99:F6:
  • 9C:D0:DD:10:A3:F1:2E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
  • EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
  • Timestamp : Jan 4 15:46:13.503 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:42:53:24:FD:21:1F:F1:86:B1:6D:93:21:
  • D0:B5:ED:2A:FF:F1:38:2C:AE:15:56:EB:BE:0A:EC:17:
  • 53:1D:E7:06:02:20:10:31:86:EE:C6:F0:26:CF:BA:0F:
  • 75:2B:85:98:EF:6E:D6:7E:35:19:4F:36:5E:F9:0E:AC:
  • C3:6E:06:99:BF:CE