SSL Server Test: esquivelautopartes.com.mx (Powered by Qualys SSL Labs)

SSL Report: esquivelautopartes.com.mx (200.56.117.229)

Assessed on: Fri, 05 Sep 2025 08:38:13 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

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 supports SSL 2, which is obsolete and insecure, and can be used against TLS (DROWN attack). Grade set to F. MORE INFO »

This server supports insecure cipher suites (see below for details). Grade set to F.

This server supports insecure Diffie-Hellman (DH) key exchange parameters (Logjam). Grade set to F. MORE INFO »

This server supports 512-bit export suites and might be vulnerable to the FREAK attack. Grade set to F. MORE INFO »

This server is vulnerable to the POODLE attack. If possible, disable SSL 3 to mitigate. Grade capped to C. MORE INFO »

This server is vulnerable to MITM attacks because it supports insecure renegotiation. Grade set to F.

The server supports only older protocols, but not the current best TLS 1.2 or TLS 1.3. Grade capped to C. MORE INFO »

The server private key is not strong enough. Grade capped to B.

This server accepts RC4 cipher, but only with older protocols. Grade capped to B. 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 1024 bits (SHA1withRSA)

Server Key and Certificate #1
Subject	boveda.kes.net Fingerprint SHA256: 1c3bcdb996eb694f272f7fb33467cd8f31207b5ad4896af87b51a8a564060e78 Pin SHA256: NLpv9qK8+P54M1RwiLg97BZSKFchpD6Z34mg5WSb9qk=
Common names	boveda.kes.net
Alternative names	- INVALID
Serial Number	00d57dba0137b9cc00
Valid from	Wed, 16 Apr 2025 03:00:07 UTC
Valid until	Thu, 16 Apr 2026 03:00:07 UTC (expires in 7 months and 10 days)
Key	RSA 1024 bits (e 65537) WEAK
Weak key (Debian)	No
Issuer	boveda.kes.net 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 (716 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	boveda.kes.net Self-signed Fingerprint SHA256: 1c3bcdb996eb694f272f7fb33467cd8f31207b5ad4896af87b51a8a564060e78 Pin SHA256: NLpv9qK8+P54M1RwiLg97BZSKFchpD6Z34mg5WSb9qk= RSA 1024 bits (e 65537) / SHA1withRSA WEAK KEY 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	boveda.kes.net Self-signed Fingerprint SHA256: 1c3bcdb996eb694f272f7fb33467cd8f31207b5ad4896af87b51a8a564060e78 Pin SHA256: NLpv9qK8+P54M1RwiLg97BZSKFchpD6Z34mg5WSb9qk= RSA 1024 bits (e 65537) / SHA1withRSA WEAK KEY 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	boveda.kes.net Self-signed Fingerprint SHA256: 1c3bcdb996eb694f272f7fb33467cd8f31207b5ad4896af87b51a8a564060e78 Pin SHA256: NLpv9qK8+P54M1RwiLg97BZSKFchpD6Z34mg5WSb9qk= RSA 1024 bits (e 65537) / SHA1withRSA WEAK KEY 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	boveda.kes.net Self-signed Fingerprint SHA256: 1c3bcdb996eb694f272f7fb33467cd8f31207b5ad4896af87b51a8a564060e78 Pin SHA256: NLpv9qK8+P54M1RwiLg97BZSKFchpD6Z34mg5WSb9qk= RSA 1024 bits (e 65537) / SHA1withRSA WEAK KEY 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	boveda.kes.net Self-signed Fingerprint SHA256: 1c3bcdb996eb694f272f7fb33467cd8f31207b5ad4896af87b51a8a564060e78 Pin SHA256: NLpv9qK8+P54M1RwiLg97BZSKFchpD6Z34mg5WSb9qk= RSA 1024 bits (e 65537) / SHA1withRSA WEAK KEY 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 INSECURE	Yes
SSL 2 INSECURE	Yes

Cipher Suites
# TLS 1.0 (server has no preference)
TLS_RSA_EXPORT_WITH_RC4_40_MD5 (`0x3`) INSECURE	40
TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (`0x6`) INSECURE	40
TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (`0x8`) INSECURE	40
TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (`0x14`) DH 512 bits FS INSECURE	40
TLS_RSA_WITH_DES_CBC_SHA (`0x9`) INSECURE	56
TLS_DHE_RSA_WITH_DES_CBC_SHA (`0x15`) DH 1024 bits FS INSECURE	56
TLS_RSA_EXPORT1024_WITH_RC4_56_MD5 (`0x60`) INSECURE	56
TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 (`0x61`) INSECURE	56
TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA (`0x62`) INSECURE	56
TLS_RSA_EXPORT1024_WITH_RC4_56_SHA (`0x64`) INSECURE	56
TLS_RSA_WITH_3DES_EDE_CBC_SHA (`0xa`) WEAK	112
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (`0x16`) DH 1024 bits FS WEAK	112
TLS_RSA_WITH_AES_128_CBC_SHA (`0x2f`) WEAK	128
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (`0x33`) DH 1024 bits FS WEAK	128
TLS_RSA_WITH_RC4_128_MD5 (`0x4`) INSECURE	128
TLS_RSA_WITH_RC4_128_SHA (`0x5`) INSECURE	128
TLS_RSA_WITH_IDEA_CBC_SHA (`0x7`) WEAK	128
TLS_RSA_WITH_AES_256_CBC_SHA (`0x35`) WEAK	256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (`0x39`) DH 1024 bits FS WEAK	256
# SSL 3 (server has no preference)
TLS_RSA_EXPORT_WITH_RC4_40_MD5 (`0x3`) INSECURE	40
TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (`0x6`) INSECURE	40
TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (`0x8`) INSECURE	40
TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (`0x14`) DH 512 bits FS INSECURE	40
TLS_RSA_WITH_DES_CBC_SHA (`0x9`) INSECURE	56
TLS_DHE_RSA_WITH_DES_CBC_SHA (`0x15`) DH 1024 bits FS INSECURE	56
TLS_RSA_EXPORT1024_WITH_RC4_56_MD5 (`0x60`) INSECURE	56
TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 (`0x61`) INSECURE	56
TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA (`0x62`) INSECURE	56
TLS_RSA_EXPORT1024_WITH_RC4_56_SHA (`0x64`) INSECURE	56
TLS_RSA_WITH_3DES_EDE_CBC_SHA (`0xa`) WEAK	112
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (`0x16`) DH 1024 bits FS WEAK	112
TLS_RSA_WITH_AES_128_CBC_SHA (`0x2f`) WEAK	128
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (`0x33`) DH 1024 bits FS WEAK	128
TLS_RSA_WITH_RC4_128_MD5 (`0x4`) INSECURE	128
TLS_RSA_WITH_RC4_128_SHA (`0x5`) INSECURE	128
TLS_RSA_WITH_IDEA_CBC_SHA (`0x7`) WEAK	128
TLS_RSA_WITH_AES_256_CBC_SHA (`0x35`) WEAK	256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (`0x39`) DH 1024 bits FS WEAK	256
# SSL 2 (client selects suite)
SSL_CK_RC4_128_WITH_MD5 (`0x10080`) INSECURE	128
SSL_CK_RC4_128_EXPORT40_WITH_MD5 (`0x20080`) INSECURE	40
SSL_CK_RC2_128_CBC_WITH_MD5 (`0x30080`) INSECURE	128
SSL_CK_RC2_128_CBC_EXPORT40_WITH_MD5 (`0x40080`) INSECURE	40
SSL_CK_IDEA_128_CBC_WITH_MD5 (`0x50080`) INSECURE	128
SSL_CK_DES_64_CBC_WITH_MD5 (`0x60040`) INSECURE	56
SSL_CK_DES_192_EDE3_CBC_WITH_MD5 (`0x700c0`) INSECURE	112
SSL_CK_RC4_64_WITH_MD5 (`0x80080`) INSECURE	64

Handshake Simulation
Android 2.3.7 No SNI ²	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_RC4_128_MD5 No FS RC4
Android 4.0.4	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Android 4.1.1	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Android 4.2.2	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Android 4.3	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Android 4.4.2	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Android 5.0.0	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Android 6.0	Server closed connection
Android 7.0	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
Android 8.0	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
Android 8.1	Server closed connection
Android 9.0	Server closed connection
Baidu Jan 2015	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
BingPreview Jan 2015	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Chrome 49 / XP SP3	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Chrome 69 / Win 7 R	Server closed connection
Chrome 70 / Win 10	Server closed connection
Chrome 80 / Win 10 R	Server closed connection
Firefox 31.3.0 ESR / Win 7	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_128_CBC_SHA DH 1024 FS
Firefox 47 / Win 7 R	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_128_CBC_SHA DH 1024 FS
Firefox 49 / XP SP3	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_128_CBC_SHA DH 1024 FS
Firefox 62 / Win 7 R	Server closed connection
Firefox 73 / Win 10 R	Server closed connection
Googlebot Feb 2018	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
IE 6 / XP No FS ¹ No SNI ²	RSA 1024 (SHA1)	SSL 3	TLS_RSA_WITH_RC4_128_MD5 RC4
IE 7 / Vista	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
IE 8 / XP No FS ¹ No SNI ²	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_RC4_128_MD5 RC4
IE 8-10 / Win 7 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
IE 11 / Win 7 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
IE 11 / Win 8.1 R	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
IE 10 / Win Phone 8.0	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
IE 11 / Win Phone 8.1 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
IE 11 / Win Phone 8.1 Update R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
IE 11 / Win 10 R	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Edge 15 / Win 10 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Edge 16 / Win 10 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Edge 18 / Win 10 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Edge 13 / Win Phone 10 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Java 6u45 No SNI ²	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_RC4_128_MD5 No FS RC4
Java 7u25	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
Java 8u161	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Java 11.0.3	Server closed connection
Java 12.0.1	Server closed connection
OpenSSL 0.9.8y	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
OpenSSL 1.0.1l R	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
OpenSSL 1.0.2s R	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
OpenSSL 1.1.0k R	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
OpenSSL 1.1.1c R	Server closed connection
Safari 5.1.9 / OS X 10.6.8	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
Safari 6 / iOS 6.0.1	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
Safari 6.0.4 / OS X 10.8.4 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
Safari 7 / iOS 7.1 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_128_CBC_SHA No FS
Safari 7 / OS X 10.9 R	Server closed connection
Safari 8 / iOS 8.4 R	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Safari 8 / OS X 10.10 R	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
Safari 9 / iOS 9 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Safari 9 / OS X 10.11 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Safari 10 / iOS 10 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Safari 10 / OS X 10.12 R	RSA 1024 (SHA1)	TLS 1.0	TLS_RSA_WITH_AES_256_CBC_SHA No FS
Safari 12.1.2 / MacOS 10.14.6 Beta R	Server closed connection
Safari 12.1.1 / iOS 12.3.1 R	Server closed connection
Yahoo Slurp Jan 2015	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
YandexBot Jan 2015	RSA 1024 (SHA1)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 1024 FS
# Not simulated clients (Protocol mismatch)
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
Secure Renegotiation	Not supported ACTION NEEDED (more info)
Secure Client-Initiated Renegotiation	No
Insecure Client-Initiated Renegotiation	Supported INSECURE (more info)
BEAST attack	Not mitigated server-side (more info) SSL 3: `0x6`, TLS 1.0: `0x6`
POODLE (SSLv3)	Vulnerable INSECURE (more info) SSL 3: `0x6`
POODLE (TLS)	No (more info)
Zombie POODLE	No (more info) TLS 1.0 : `0x000a`
GOLDENDOODLE	No (more info) TLS 1.0 : `0x000a`
OpenSSL 0-Length	No (more info) TLS 1.0 : `0x000a`
Sleeping POODLE	No (more info) TLS 1.0 : `0x000a`
Downgrade attack prevention	No, TLS_FALLBACK_SCSV not supported (more info)
SSL/TLS compression	No
RC4	Yes INSECURE (more info)
Heartbeat (extension)	No
Heartbleed (vulnerability)	No (more info)
Ticketbleed (vulnerability)	No (more info)
OpenSSL CCS vuln. (CVE-2014-0224)	Probably, but not exploitable (investigate to confirm and patch) (more info)
OpenSSL Padding Oracle vuln. (CVE-2016-2107)	No (more info)
ROBOT (vulnerability)	No (more info)
Forward Secrecy	Insecure key exchange INSECURE
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	Yes Replace with custom DH parameters if possible (more info)
DH public server param (Ys) reuse	No
ECDH public server param reuse	No, ECDHE suites not supported
Supported Named Groups	-
SSL 2 handshake compatibility	Yes

HTTP Requests

1 https://esquivelautopartes.com.mx/ (HTTP/1.1 200 OK)
1
	Date	Fri, 05 Sep 2025 07:34:53 GMT
	Server	Apache
	Last-Modified	Fri, 12 Apr 2013 19:07:24 GMT
	ETag	"24a0885-1c9-51685b6c"
	Accept-Ranges	bytes
	Content-Length	457
	Connection	close
	Content-Type	text/html

Miscellaneous
Test date	Fri, 05 Sep 2025 08:36:27 UTC
Test duration	106.329 seconds
HTTP status code	200
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.1

Copyright © 2009-2025 Qualys, Inc. All Rights Reserved. Privacy Policy.	Terms and Conditions
Try Qualys for free! Experience the award-winning Qualys Cloud Platform and the entire collection of Qualys Cloud Apps, including certificate security solutions.