SSL Report:
qoatti.tgscolombia.com
(45.239.115.137)
Assessed on: Wed, 11 Jun 2025 17:09:39 UTC
| Clear cache
Summary
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.
This server does not support Forward Secrecy with the reference browsers.
Grade capped to B.
MORE INFO »
This server's certificate chain is incomplete. Grade capped to B.
This server does not support TLS 1.3. MORE INFO »
HTTP Strict Transport Security (HSTS) with long duration deployed on this server.
MORE INFO »
DNS Certification Authority Authorization (CAA) Policy found for this domain.
MORE INFO »
Certificate #1: RSA 4096 bits (SHA256withRSA)
|
Server Key and Certificate #1
|
|
| Subject |
*.tgscolombia.com
Fingerprint SHA256: 2ba851efe02953fbf6841d40c91666499279ff2e7f1c961ff065930b59e8eec4 Pin SHA256: r9F6sGKqSDTXP9wP7eCywlNeIjD6Zx1DWNbw+XM8K9U= |
| Common names | *.tgscolombia.com |
| Alternative names | *.tgscolombia.com tgscolombia.com |
| Serial Number | 0d12bda0f8b7fce0 |
| Valid from | Wed, 24 Jul 2024 21:55:09 UTC |
| Valid until | Mon, 25 Aug 2025 21:55:09 UTC (expires in 2 months and 14 days) |
| Key | RSA 4096 bits (e 65537) |
| Weak key (Debian) | No |
| Issuer | Go Daddy Secure Certificate Authority - G2
AIA: http://certificates.godaddy.com/repository/gdig2.crt |
| Signature algorithm | SHA256withRSA |
| Extended Validation | No |
| Certificate Transparency | Yes (certificate) |
| OCSP Must Staple | No |
| Revocation information |
CRL, OCSP CRL: http://crl.godaddy.com/gdig2s1-26392.crl OCSP: http://ocsp.godaddy.com/ |
| Revocation status | Revoked INSECURE |
| DNS CAA | Yes policy host: qoatti.tgscolombia.com issue: godaddy.com flags:0 |
| Trusted | No NOT TRUSTED
(Why?)
Mozilla Apple Android Java Windows |
Certification Paths |
Certificate #2: RSA 4096 bits (SHA256withRSA)
No SNI
|
Server Key and Certificate #1
|
|
| Subject |
*.tgscolombia.com
Fingerprint SHA256: 2ba851efe02953fbf6841d40c91666499279ff2e7f1c961ff065930b59e8eec4 Pin SHA256: r9F6sGKqSDTXP9wP7eCywlNeIjD6Zx1DWNbw+XM8K9U= |
| Common names | *.tgscolombia.com |
| Alternative names | *.tgscolombia.com tgscolombia.com |
| Serial Number | 0d12bda0f8b7fce0 |
| Valid from | Wed, 24 Jul 2024 21:55:09 UTC |
| Valid until | Mon, 25 Aug 2025 21:55:09 UTC (expires in 2 months and 14 days) |
| Key | RSA 4096 bits (e 65537) |
| Weak key (Debian) | No |
| Issuer | Go Daddy Secure Certificate Authority - G2
AIA: http://certificates.godaddy.com/repository/gdig2.crt |
| Signature algorithm | SHA256withRSA |
| Extended Validation | No |
| Certificate Transparency | Yes (certificate) |
| OCSP Must Staple | No |
| Revocation information |
CRL, OCSP CRL: http://crl.godaddy.com/gdig2s1-26392.crl OCSP: http://ocsp.godaddy.com/ |
| Revocation status | Revoked INSECURE |
| Trusted | No NOT TRUSTED
(Why?)
Mozilla Apple Android Java Windows |
|
Certification Paths |
Configuration
| Protocols | |
| TLS 1.3 | No |
| TLS 1.2 | Yes* |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 | No |
| SSL 2 | No |
| (*) Experimental: Server negotiated using No-SNI | |
| Cipher Suites | ||
|
# TLS 1.2 (suites in server-preferred order)
|
||
TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c)
WEAK
|
128 | |
TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c)
WEAK
|
128 | |
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d)
WEAK
|
256 | |
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d)
WEAK
|
256 | |
| Handshake Simulation | |||
| Android 4.4.2 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Android 5.0.0 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Android 6.0 | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Android 7.0 | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Android 8.0 | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Android 8.1 | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Android 9.0 | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| BingPreview Jan 2015 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Chrome 49 / XP SP3 | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Chrome 69 / Win 7 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Chrome 70 / Win 10 | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Chrome 80 / Win 10 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| Firefox 31.3.0 ESR / Win 7 |
Server sent fatal alert: handshake_failure |
||
| Firefox 47 / Win 7 R |
Server sent fatal alert: handshake_failure |
||
| Firefox 49 / XP SP3 |
Server sent fatal alert: handshake_failure |
||
| Firefox 62 / Win 7 R |
Server sent fatal alert: handshake_failure |
||
| Firefox 73 / Win 10 R |
Server sent fatal alert: handshake_failure |
||
| Googlebot Feb 2018 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_GCM_SHA256 No FS |
| IE 11 / Win 7 R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| IE 11 / Win 8.1 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| IE 11 / Win Phone 8.1 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| IE 11 / Win Phone 8.1 Update R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| IE 11 / Win 10 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Edge 15 / Win 10 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Edge 16 / Win 10 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Edge 18 / Win 10 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Edge 13 / Win Phone 10 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Java 8u161 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Java 11.0.3 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Java 12.0.1 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| OpenSSL 1.0.1l R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| OpenSSL 1.0.2s R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| OpenSSL 1.1.0k R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| OpenSSL 1.1.1c R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 6 / iOS 6.0.1 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 7 / iOS 7.1 R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 7 / OS X 10.9 R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 8 / iOS 8.4 R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 8 / OS X 10.10 R | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 9 / iOS 9 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 9 / OS X 10.11 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 10 / iOS 10 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 10 / OS X 10.12 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 12.1.2 / MacOS 10.14.6 Beta R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Safari 12.1.1 / iOS 12.3.1 R | RSA 4096 (SHA256) | TLS 1.2 > http/1.1 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| Apple ATS 9 / iOS 9 R |
Server sent fatal alert: handshake_failure |
||
| Yahoo Slurp Jan 2015 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
| YandexBot Jan 2015 | RSA 4096 (SHA256) | TLS 1.2 | TLS_RSA_WITH_AES_128_CBC_SHA256 No FS |
|
# Not simulated clients (Protocol mismatch)
|
|||
| Android 2.3.7 No SNI 2 |
Protocol mismatch (not simulated) |
||
| Android 4.0.4 |
Protocol mismatch (not simulated) |
||
| Android 4.1.1 |
Protocol mismatch (not simulated) |
||
| Android 4.2.2 |
Protocol mismatch (not simulated) |
||
| Android 4.3 |
Protocol mismatch (not simulated) |
||
| Baidu Jan 2015 |
Protocol mismatch (not simulated) |
||
| IE 6 / XP No FS 1 No SNI 2 |
Protocol mismatch (not simulated) |
||
| IE 7 / Vista |
Protocol mismatch (not simulated) |
||
| IE 8 / XP No FS 1 No SNI 2 |
Protocol mismatch (not simulated) |
||
| IE 8-10 / Win 7 R |
Protocol mismatch (not simulated) |
||
| IE 10 / Win Phone 8.0 |
Protocol mismatch (not simulated) |
||
| Java 6u45 No SNI 2 |
Protocol mismatch (not simulated) |
||
| Java 7u25 |
Protocol mismatch (not simulated) |
||
| OpenSSL 0.9.8y |
Protocol mismatch (not simulated) |
||
| Safari 5.1.9 / OS X 10.6.8 |
Protocol mismatch (not simulated) |
||
| Safari 6.0.4 / OS X 10.8.4 R |
Protocol mismatch (not simulated) |
||
| (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 | |
| Secure Renegotiation | Supported |
| Secure Client-Initiated Renegotiation | No |
| Insecure Client-Initiated Renegotiation | No |
| BEAST attack | Mitigated server-side (more info) |
| POODLE (SSLv3) | No, SSL 3 not supported (more info) |
| POODLE (TLS) | No (more info) |
| Zombie POODLE | No (more info)
TLS 1.2 : 0x003c
|
| GOLDENDOODLE | No (more info)
TLS 1.2 : 0x003c
|
| OpenSSL 0-Length | No (more info)
TLS 1.2 : 0x003c
|
| Sleeping POODLE | No (more info)
TLS 1.2 : 0x003c
|
| 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) | No (more info) |
| Forward Secrecy | No WEAK (more info) |
| ALPN | Yes http/1.1 |
| NPN | No |
| Session resumption (caching) | No (IDs empty) |
| Session resumption (tickets) | No |
| OCSP stapling | No |
| Strict Transport Security (HSTS) | Yes
max-age=63072000; includeSubdomains; |
| 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 | No |
| 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 | No |
|
HTTP Requests
|
|
1 https://qoatti.tgscolombia.com/
(HTTP/1.1 403 Forbidden)
| 1 | |
| Date | Wed, 11 Jun 2025 17:07:55 GMT | |
| Server | Apache | |
| X-Frame-Options | SAMEORIGIN, SAMEORIGIN | |
| Strict-Transport-Security | max-age=63072000; includeSubdomains; | |
| X-XSS-Protection | 1; mode=block | |
| X-Content-Type-Options | nosniff | |
| Content-Security-Policy | style-src 'self' 'unsafe-inline' https://cdn.www.gov.co/assets/css/styles.css https://unpkg.com/gijgo@1.9.13/css/gijgo.min.css https://cdn.www.gov.co/layout/v4/all.css https://cdn.www.gov.co/v3/assets/cdn.min.css https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/css/bootstrap.min.css https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css; | |
| Referrer-Policy | same-origin | |
| Permissions-Policy | accelerometer=(),autoplay=(),camera=(),encrypted-media=(),fullscreen=*,geolocation=*,gyroscope=(),interest-cohort=(),magnetometer=(),microphone=(),midi=(),payment=("https://*.paypal.com" "https://*.barion.com"),sync-xhr=*,usb=(),xr-spatial-tracking=() | |
| Content-Length | 199 | |
| Connection | close | |
| Content-Type | text/html; charset=iso-8859-1 | |
| Miscellaneous | |
| Test date | Wed, 11 Jun 2025 17:07:27 UTC |
| Test duration | 132.87 seconds |
| HTTP status code | 403 |
| HTTP server signature | Apache |
| 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:
- Invalid certificate
- Invalid configuration
- Unknown Certificate Authority
1. Invalid certificate
A certificate is invalid if:
- It is used before its activation date
- It is used after its expiry date
- Certificate hostnames don't match the site hostname
- It has been revoked
- It has insecure signature
- It has been blacklisted
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.0