Please make custom website urls HTTPS COMPLIANT
The last post about this is from 2017 and the follow-up comments in the last 2 years have not been responded to. Please make the custom URLs HTTPS! We have paid extra to customize the URL and it literally costs nothing to add HTTPS. (I added it to my personal work website for free!)
Hi and thank you so much for your idea!
We will definitely take this into consideration. We’re always trying to improve the Wedding Website experience for couples so we welcome all of your great ideas.
We will keep this forum updated as we make improvements!
Enjoy your planning!
Your Customer Experience Team
Ian Yates commented
As of July 2018, all users who access custom domain implementations on theknot.com from google Chrome web browser (the Google Chrome web browser has a market share of 68.91% as of this posting) will see "Not secure" in the URL bar. Other browsers have similar warnings as well.
See the google chrome blog article on this issue here: https://www.blog.google/products/chrome/milestone-chrome-security-marking-http-not-secure/
SSL on all sites has been industry standard for several years, and is now an expectation, and should not be considered an optional feature.
SSL implementations can be done for FREE with very little effort on most platforms, so there is no excuse for not having SSL.
Bill Gates commented
Please support https already. Come on.
Has this been resolved? If not I am going to have to move my wedding website elsewhere because this is really not safe.
Sad. Please support https asap
It's troubling that in 2020 this is an issue. It's literally free to add. Will not recommend customer urls (which is a super cool) if this is not resolved.
E Brown commented
Has this been resolved? We are having the same issue. Seems crazy that they can't secure it. Let me know if anyone has been able to fix it, otherwise we will have to switch to Zola.
Are there any updates regarding enabling SSL for the websites. I created a domain on for my wedding website, but https doesn't work.
Randall Hunt commented
This really needs to happen if you want technology folks to use your site. I purchased a domain (b/c I couldn't use the one I already purchased b/c you won't allow us to just change to your nameservers...) and then I find out I can't even have HTTPs on the domain?
It makes me want a refund and I want the domain released to me, to be honest.
Zola does this right though. I think enabling custom domain flexibility and HTTPS should be a priority that will help with your sales pipeline.
You could implement this with route53 on AWS in a few minutes.
Jitendra Kumar Dash commented
Are you planning to make custom domain site https compliant?
This absolutely needs to be addressed, especially if guests are giving monetary gifts using the funds option. Where are we at with this given the request was submitted 6 months ago.
After purchasing a wedding website, it should have a secure domain but it doesn't. That opens up a lot of security risks by linking a registry or asking for guests to send monetary gifts via the funds option. The site should be secure to minimize the possibility of fraud or hacking.
Brad Clark commented
Really shocked that there is no https for custom domains. Please enabled this ASAP. Let's encrypt and cloudflare have free/cheap TLS certificates and I'm sure many customers, including myself, would pay.
I also think this needs to be addressed.
Oliver Johnson commented
I want to use lifecake primarily as a sort of diary for myself, but the sharing with relatives function is completely taking over (some relatives cannot contain themselves and compulsively comment and like every single post). It would be very useful to just turn off the feature completely.
Oliver Johnson commented
Until this is addressed, can you provide any reassurance that my wedding website isn't going to be hacked? Otherwise, can you please direct me to a portal to get a refund?
What Kyle said - if this is not resolved we'll need to go a different route on our wedding website. We cannot reasonably ask our guests to RSVP without a secure connection. It's somewhat absurd that you're charging as much as you do for a custom URL and then not providing a secure link.
Not only does the https:// without www not work, but the https:// with www throws a warning message. This is DNS 101 and needs to be resolved immediately.
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.
This isn't so much related to "Wedding Website experience" for couples as it is a the "security and privacy experience" for all of the friends and family members. Until this is addressed, can you provide any reassurance that my wedding website isn't going to be hacked (exposing the PII contained in my private attendee list, for instance)? Otherwise, can you please direct me to a portal to get a refund? I'd rather not put my friends and family at risk because theknot.com chooses not to make security a priority.
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?