SSL-Tools

SSL check results of studhub.vip

NEW You can also bulk check multiple servers.

Discover if the mail servers for studhub.vip 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, 21 Oct 2024 00:30:44 +0000

We can not guarantee a secure connection to the mailservers of studhub.vip!

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

/mailservers/studhub.vip

Servers

Incoming Mails

These servers are responsible for incoming mails to @studhub.vip addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.studhub.vip
2a01:239:353:c700::1
Results incomplete
1
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.studhub.vip
87.106.80.158
 1
supported
mail.studhub.vip
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.studhub.vip

Certificate chain
  • mail.studhub.vip
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.studhub.vip
Alternative Names
  • mail.studhub.vip
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-10-16
Not valid after
2025-01-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
47:EB:9A:D7:39:43:CC:B8:21:B1:55:C3:E9:ED:DB:AA:09:64:AB:13:D4:26:FE:DB:F2:E9:85:04:5A:FF:EA:68
SHA1
0D:D0:59:55:86:CF:99:0C:AD:54:0C:32:9B:A7:17:D8:30:54:AF:45
X509v3 extensions
subjectKeyIdentifier
  • D5:B3:B5:35:F9:17:FA:07:E5:D7:9E:E8:45:95:89:DD:93:C3:63:87
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Oct 16 16:10:55.850 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:97:B9:D3:64:0D:1E:AC:EF:5B:04:B7:
  • 9D:23:57:9B:D2:0F:94:D3:3B:66:93:22:B0:18:2E:4E:
  • 67:5D:05:69:71:02:20:3D:A8:81:4A:EE:CB:B9:B3:4F:
  • 4C:43:09:F8:AC:62:59:6A:1E:86:B3:96:B7:92:52:B7:
  • 1F:05:ED:BD:AB:EA:63
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 16 16:10:55.908 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4A:8C:50:61:C9:16:24:25:31:46:7C:F2:
  • 7B:7F:90:EE:E5:53:C9:70:CF:D1:75:09:3D:62:C1:1B:
  • 5F:9A:D9:CB:02:20:7D:D8:D9:AE:32:ED:D8:BC:B0:21:
  • EE:68:5E:1D:E6:11:40:C5:90:53:0E:BF:A5:1D:40:B5:
  • 9A:0A:B8:CB:21:13