Beginning in 2018, Google Chrome began marking all websites that do not use HTTPS encryption as “not secure” for all site visitors. To make your MemberClicks web pages more secure and avoid this designation, we will be enabling an automated redirect of all non-secure pages to a secure version of your URLs. The steps below are required before we can enable this service.
What does my DNS provider need to change?
Your DNS provider will need to complete the following:
- Remove current A records pointing to WebLink for all site domains where the IP Address begins with:
Note: Do not change any WebLink A-Records with an IP Address of: 22.214.171.124
- Add a CNAME record for all site domains that were removed, pointing to your organization's unique organization.weblinkconnect.com domain. If you have not received an email with this information, please contact Support.
Do I need to do anything after my DNS provider makes these changes?
Once the steps above have been completed with your DNS provider, please contact WebLink support to notify us that the change has been made so that we can complete the HTTPS activation on our end.
After that, you will be able to use "HTTPS" in front of any of your WebLink web pages (for example your online directory, events calendar, etc) and the pages will use secure encryption and render the "Secure" designation on Google Chrome version 68+. This includes any sub-domain pages (e.g. web.yourdomain.com). Please refer to the later sections of this article for instructions on how to update your links.
Who manages my DNS?
If you aren’t sure who manages your DNS, visit www.whois.com and enter your website domain name. If your Name Servers are as listed below, then you will not need to take any action because we will make the changes for you:
If your Name Servers do not match the above, WebLink does not manage your DNS. In this case you should check your website domain host (e.g. GoDaddy, Network Solutions, eNom, etc.) first and/or contact your third-party IT Support or Website Developer for assistance in making the changes to your DNS records.
Why is this changing?
Click here for more information about DNS and the migration to a secure web.