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.
I see it is fine on web however the mobile version, if you try does not display the lock, and I have tried all possible options that I can think of, please help.
Okay I will have a look. I am usign the good cloud platform so the ip address but it is masked to point to sphacor.com. I will also check the link you provided.
Ok I had a look but here my concern is, that I have created the SSL certificate using sphacor.com wherease I see that other folks are seeing IP address. Now the IP address does not have the SSl attached whereas the sphacor.com domain is. This ip points to the sphacor.com.
There are 3 areas of concern here. One is that image that @Rip pointed out above.
Another image, is the WhatsApp image - also served over http. http://35.222.17.137/wp-content/uploads/2021/08/WhatsApp-Image-2021-08-21-at-15.00.31.jpeg
The 3rd is that you have TSLv1.0, v1.1 & v1.3 enabled. You should disable TSLv1.0. Web browsers, especially some mobile browsers will simply refuse to connect to your site if TSLv1.0 is being served. It is no longer secure.
Thank guys for the help and input. I am kind of new to this web word and so I not well acqauinted here. I am sorry but the image you have mentioned about, may I know how that image i sa matter of concern? And in this case why SSL is behaving separately on web versus mobile if that image was the matter of concern t? U will also look at the TSLv1 as well.
Looking the beginning of the URLs for both images, you'll see they begin with http and not https. That's the problem. It's called mixed content. The http links are unsecure. Change those two links from http to https and that should clear that up.