Your connection is not fully secure
This site uses an outdated security configuration, which may expose your information (for example, passwords, messages, or credit cards) when it is sent to this site.
NET::ERR_SSL_OBSOLETE_VERSION
The connection used to load this site used TLS 1.0 or TLS 1.1, which are deprecated and will be disabled in the future. Once disabled, users will be prevented from loading this site. The server should enable TLS 1.2 or later.
Proceed to www.daddydater.com (unsafe)
Will they ever spend the $6 & up to get an SSL certificate?
Any idea on how long it will take to fix the problem?
It really messes with loading the site & sometimes Google chrome rejects the site.
I know what needs to be done & it not that hard to et it done.
Do you need help?
Peter
1) What is being done to make this site secure and when will it happen?
2) How can I delete my profile and end my participation in this site? I'd like to remove all information from the site if it is not secure.
THANKS
I have about a dozen site I help & I've installed & help upgrade their site's to go secure. These days the cost to buy a New SSL certificate is under $15, some acs cheap as $6.
Do you need help?
1 They have a valid certificate, but it expires in 20 days. This link will tell you all: https://www.sslshopper.com/ssl-checker.html#hostn … ydater.com
2- they could go to https://store.ssl2buy.com/ but a new certificate for $5 or more depending on the type of certificate they want.
3- First they need to look at their setup & coding. Somewhere in their scripts it calling for some of the files they are loading from unsecure locations. 1 non secure call, ruins the https:
4 - I did find this line at very top of their pages wrong. it the line that sets up on the page is to respond in browsers. it calls "
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">"
Then there are other calls to non https within the pages
5- I would be happy to help debug the issue for them if they like. I tried contacting them about it but never got a response.
Peter
We’re on it and will be fixed shortly