SSL Report: webvpn.dch.cantv.com.ve (190.9.129.50)
Assessed on:  Mon, 28 Jul 2025 02:39:11 UTC | Clear cache

Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Summary
Overall Rating
F
0
20
40
60
80
100
Certificate
 
Protocol Support
 
Key Exchange
 
Cipher Strength
 

Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.
This server's certificate is not trusted, see below for details.
Certificate uses an insecure signature. Upgrade to SHA2 to avoid browser warnings.  MORE INFO »
This server is vulnerable to the POODLE TLS attack. Patching required. Grade set to F. MORE INFO »
This server is vulnerable to the Return Of Bleichenbacher's Oracle Threat (ROBOT) vulnerability. Grade set to F.  MORE INFO »
This server is vulnerable to the Zombie POODLE vulnerability. Grade set to F.  MORE INFO »
This server is vulnerable to the Sleeping POODLE vulnerability. Grade set to F.  MORE INFO »
The server supports only older protocols, but not the current best TLS 1.2 or TLS 1.3. Grade capped to C.  MORE INFO »
There is no support for secure renegotiation.  MORE INFO »
This server does not support Forward Secrecy with the reference browsers. Grade capped to B.  MORE INFO »
This server does not support Authenticated encryption (AEAD) cipher suites. Grade capped to B.  MORE INFO »
This server supports TLS 1.0. Grade capped to B. MORE INFO »
This server does not support TLS 1.3.  MORE INFO »
Certificate #1: RSA 2048 bits (SHA1withRSA)
Server Key and Certificate #1
Subject webvpn.dch.cantv.com.ve
Fingerprint SHA256: 71dad530e20d03fa09804ae1b0e5f493dfc9143230d703dddb45ecc521c68a1c
Pin SHA256: pxMIaVFoqGY/UaaSneeA1GgPwfyibt31H9ViQVaPi2E=
Common names webvpn.dch.cantv.com.ve
Alternative names -   INVALID
Serial Number bba03059 INVALID
Valid from Thu, 01 Jun 2017 23:45:48 UTC
Valid until Sun, 30 May 2027 23:45:48 UTC (expires in 1 year and 10 months)
Key RSA 2048 bits (e 65537)
Weak key (Debian) No
Issuer webvpn.dch.cantv.com.ve   Self-signed
Signature algorithm SHA1withRSA   INSECURE
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information None
DNS CAA No (more info)
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 1 (1121 bytes)
Chain issues None


Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store
webvpn.dch.cantv.com.ve   Self-signed
Fingerprint SHA256: 71dad530e20d03fa09804ae1b0e5f493dfc9143230d703dddb45ecc521c68a1c
Pin SHA256: pxMIaVFoqGY/UaaSneeA1GgPwfyibt31H9ViQVaPi2E=

RSA 2048 bits (e 65537) / SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store
webvpn.dch.cantv.com.ve   Self-signed
Fingerprint SHA256: 71dad530e20d03fa09804ae1b0e5f493dfc9143230d703dddb45ecc521c68a1c
Pin SHA256: pxMIaVFoqGY/UaaSneeA1GgPwfyibt31H9ViQVaPi2E=

RSA 2048 bits (e 65537) / SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store
webvpn.dch.cantv.com.ve   Self-signed
Fingerprint SHA256: 71dad530e20d03fa09804ae1b0e5f493dfc9143230d703dddb45ecc521c68a1c
Pin SHA256: pxMIaVFoqGY/UaaSneeA1GgPwfyibt31H9ViQVaPi2E=

RSA 2048 bits (e 65537) / SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store
webvpn.dch.cantv.com.ve   Self-signed
Fingerprint SHA256: 71dad530e20d03fa09804ae1b0e5f493dfc9143230d703dddb45ecc521c68a1c
Pin SHA256: pxMIaVFoqGY/UaaSneeA1GgPwfyibt31H9ViQVaPi2E=

RSA 2048 bits (e 65537) / SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store
webvpn.dch.cantv.com.ve   Self-signed
Fingerprint SHA256: 71dad530e20d03fa09804ae1b0e5f493dfc9143230d703dddb45ecc521c68a1c
Pin SHA256: pxMIaVFoqGY/UaaSneeA1GgPwfyibt31H9ViQVaPi2E=

RSA 2048 bits (e 65537) / SHA1withRSA
Weak or insecure signature, but no impact on root certificate

Click here to expand

Configuration
Protocols
TLS 1.3 No
TLS 1.2 No
TLS 1.1 No
TLS 1.0 Yes
SSL 3 No
SSL 2 No


Cipher Suites
# TLS 1.0 (suites in server-preferred order)
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)   WEAK 128
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)   WEAK 256
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa)   WEAK 112


Handshake Simulation
Android 2.3.7   No SNI 2 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 4.0.4 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 4.1.1 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 4.2.2 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 4.3 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 4.4.2 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 5.0.0 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 6.0 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 7.0 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 8.0 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 8.1 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Android 9.0 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Baidu Jan 2015 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
BingPreview Jan 2015 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Chrome 49 / XP SP3 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Chrome 69 / Win 7  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Chrome 70 / Win 10 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Chrome 80 / Win 10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Firefox 31.3.0 ESR / Win 7 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Firefox 47 / Win 7  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Firefox 49 / XP SP3 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Firefox 62 / Win 7  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Firefox 73 / Win 10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Googlebot Feb 2018 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
IE 7 / Vista RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
IE 8 / XP   No FS 1   No SNI 2 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_3DES_EDE_CBC_SHA
IE 8-10 / Win 7  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
IE 11 / Win 7  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
IE 11 / Win 8.1  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
IE 10 / Win Phone 8.0 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
IE 11 / Win Phone 8.1  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
IE 11 / Win Phone 8.1 Update  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
IE 11 / Win 10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Edge 15 / Win 10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Edge 16 / Win 10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Edge 18 / Win 10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Edge 13 / Win Phone 10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Java 6u45   No SNI 2 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Java 7u25 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Java 8u161 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Java 11.0.3 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Java 12.0.1 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
OpenSSL 0.9.8y RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
OpenSSL 1.0.1l  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
OpenSSL 1.0.2s  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
OpenSSL 1.1.0k  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
OpenSSL 1.1.1c  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 5.1.9 / OS X 10.6.8 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 6 / iOS 6.0.1 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 6.0.4 / OS X 10.8.4  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 7 / iOS 7.1  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 7 / OS X 10.9  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 8 / iOS 8.4  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 8 / OS X 10.10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 9 / iOS 9  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 9 / OS X 10.11  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 10 / iOS 10  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 10 / OS X 10.12  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Safari 12.1.1 / iOS 12.3.1  R RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
Yahoo Slurp Jan 2015 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
YandexBot Jan 2015 RSA 2048 (SHA1)   TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA  No FS
# Not simulated clients (Protocol mismatch)
IE 6 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
Apple ATS 9 / iOS 9  R Protocol mismatch (not simulated)

Click here to expand

(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it.
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI.
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version.
(R) Denotes a reference browser or client, with which we expect better effective security.
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE).
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake.


Protocol Details
Renegotiation Unknown
BEAST attack Not mitigated server-side (more info)   TLS 1.0: 0x2f
POODLE (SSLv3) No, SSL 3 not supported (more info)
POODLE (TLS) Vulnerable   INSECURE (more info)
Zombie POODLE Yes   EXPLOITABLE (more info)   TLS 1.0 : 0x002f
GOLDENDOODLE No (more info)   TLS 1.0 : 0x002f
OpenSSL 0-Length No (more info)   TLS 1.0 : 0x002f
Sleeping POODLE Yes   EXPLOITABLE (more info)   TLS 1.0 : 0x002f
Downgrade attack prevention Unknown (requires support for at least two protocols, excl. SSL2)
SSL/TLS compression No
RC4 No
Heartbeat (extension) No
Heartbleed (vulnerability) No (more info)
Ticketbleed (vulnerability) No (more info)
OpenSSL CCS vuln. (CVE-2014-0224) No (more info)
OpenSSL Padding Oracle vuln.
(CVE-2016-2107)
No (more info)
ROBOT (vulnerability) Yes,  but oracle is weak (more info)
Forward Secrecy No   WEAK (more info)
ALPN No
NPN No
Session resumption (caching) No (IDs assigned but not accepted)
Session resumption (tickets) No
OCSP stapling No
Strict Transport Security (HSTS) No
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) No (more info)
Public Key Pinning Report-Only No
Public Key Pinning (Static) No (more info)
Long handshake intolerance No
TLS extension intolerance No
TLS version intolerance TLS 2.152 
Incorrect SNI alerts No
Uses common DH primes No, DHE suites not supported
DH public server param (Ys) reuse No, DHE suites not supported
ECDH public server param reuse No, ECDHE suites not supported
Supported Named Groups -
SSL 2 handshake compatibility Yes


HTTP Requests
1 https://webvpn.dch.cantv.com.ve/  (HTTP/1.1 200 OK)
1
Content-Type text/html; charset=utf-8
Transfer-Encoding chunked
Cache-Control no-cache
Pragma no-cache
Connection Keep-Alive
Date Mon, 28 Jul 2025 02:36:57 GMT
Set-Cookie tg=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure
Set-Cookie webvpn=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure
Set-Cookie webvpnc=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure
Set-Cookie webvpn_portal=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure
Set-Cookie webvpnlogin=1; path=/; secure
Set-Cookie sdesktop=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure


Miscellaneous
Test date Mon, 28 Jul 2025 02:36:46 UTC
Test duration 145.497 seconds
HTTP status code 200
HTTP server signature -
Server hostname -


Why is my certificate not trusted?

There are many reasons why a certificate may not be trusted. The exact problem is indicated on the report card in bright red. The problems fall into three categories:

  1. Invalid certificate
  2. Invalid configuration
  3. Unknown Certificate Authority

1. Invalid certificate

A certificate is invalid if:

2. Invalid configuration

In some cases, the certificate chain does not contain all the necessary certificates to connect the web server certificate to one of the root certificates in our trust store. Less commonly, one of the certificates in the chain (other than the web server certificate) will have expired, and that invalidates the entire chain.

3. Unknown Certificate Authority

In order for trust to be established, we must have the root certificate of the signing Certificate Authority in our trust store. SSL Labs does not maintain its own trust store; instead we use the store maintained by Mozilla.

If we mark a web site as not trusted, that means that the average web user's browser will not trust it either. For certain special groups of users, such web sites can still be secure. For example, if you can securely verify that a self-signed web site is operated by a person you trust, then you can trust that self-signed web site too. Or, if you work for an organisation that manages its own trust, and you have their own root certificate already embedded in your browser. Such special cases do not work for the general public, however, and this is what we indicate on our report card.

4. Interoperability issues

In some rare cases trust cannot be established because of interoperability issues between our code and the code or configuration running on the server. We manually review such cases, but if you encounter such an issue please feel free to contact us. Such problems are very difficult to troubleshoot and you may be able to provide us with information that might help us determine the root cause.

SSL Report v2.4.1