Make theknot.com HTTPS compliant
Make theknot.com HTTPS compliant. It is the standard and an expected level of security for websites these days.
Thank you for reaching out. Most of our site has been updated to be https compliant. If you find a page that is not, feel free to send me an example and I will ask our SEO team to look into this.
Our custom website domain is not compliant and this is a serious problem. We cannot reasonably ask people to RSVP on the site without it being secure, and it is throwing a warning message if someone tries to go to the https version (some browsers will force https first).
If this is not resolved, we'll need a refund on the domain and will have to move our site elsewhere.
I didn't realize that Chris and Amber have already asked about this but this is what i was hoping for. Seeing that their requests we're from over a year ago i am not reassured that this will be resolved. I actually came back to post a comment because i had heard about LetsEncrypt and it reminded me that my custom domain wedding website purchased through The Knot is not HTTPS compliant
Yeah, the customizeable domains you let people search and buy are not https. Every guest trying to view the website gets an od thin warning before they are able to proceed. Makes me feel like i paid extra to give my guests a shady experience. is this so you can get people to buy domains but then decide to go back to a free theknot.com/us/chose-a-sub-domain so that "the knot" is in once again in the URL?
I'm shocked and disappointed that although i have ticked that i don't want our site to be found in search engines, that anyone can actually see my entire wedding invite. The whole world can see it. ALL info, date, location, photos. This is a massive breach in security. My husband to be works in a pretty secretive area and this info of him CANNOT get out. Wish i had known before trusting in your site.
This a joke. The below is on your terms of service
"You may not exploit the Service to access unauthorized information."
Yet you guys have decided that even though i have not given authorization for you to exploit my privacy, you HAVE done EXACTLY that.
THIS is SO wrong.
Any update on applying an SSL certificate to a custom domain (https)? This is really important when asking guests to share their information!
Chris Snyder commented
However, when using your own domain, it is not secure. See https://www.snydersofsykesville.wedding/
I think this is very important as visitors will be entering in personal information when rsvping.