Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
CN=kingkblite.com
27.02.2020
27.05.2020
expires in 78 days kingkblite.com, www.kingkblite.com - 2 entries
both connections use that certificate. There is no mixed content reported. Not via the own parsing, not via the Screenshot creation:
Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_256_GCM.
Chrome-Resources : secure. all served securely. All resources on this page are served securely.
Some parts of the site you mentioned do have this same error, which is called a mixed content error. This is not a problem with the certificate or HTTPS setup, but with the content of the site—it’s loading subresources within the page insecurely over HTTP instead of HTTPS. An example would be if your HTML page includes something like <img src="http://example.com/image.jpg" /> instead of <img src="https://example.com/image.jpg" />, or the same for videos, scripts, frames, iframes, etc.
You can probably identify the specific problems with a tool like https://whynopadlock.com/ or with your web browser’s developer tools.
