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 WebLink 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: 126.96.36.199
- 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 WebLink 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.
Will my pages automatically use HTTPS after I make the change?
At this time, HTTP (non-secure) URLs will remain flagged as "Not Secure" and will not be automatically redirected to the HTTPS version. Until all clients have added the appropriate records, WebLink cannot automatically set your WebLink pages to use HTTPS, as this will cause issues viewing those pages for anyone without the CNAME records in place. You can use the HTTPS version, however, if you explicitly update all of your hyperlinks to use "https://" in front of the URLs.
How do I start using HTTPS Links?
If you have completed the steps above wish to start using HTTPs links for your sub-domain before July 1st, please use the Chat feature in the bottom right corner and let our WebLink Support team know you are 'Ready to use HTTPs'. Otherwise, the service will automatically switch over once all clients have completed the DNS changes.
WebLink CMS Select Customers click here to learn how to update your external links.
Here's an example:
- Your domain name for WebLink pages is web.xyzassociation.org. When you go to http://web.xyzassociation.org, the web page loads just fine, though not flagged as Secure.
- Now you try visiting https://web.xyzassociation.org. The page throws a security warning and does not load.
- You send your DNS provider the CNAME record provided to you via email. It probably looks something like this: xyzassociationINCOC.weblinkconnect.com. Then follow the steps above to remove all A records from web.xyzassociation.org (and any other hosted domains), and add a CNAME record pointing to xyzassociation.weblinkconnect.com.
- Now that your CNAME records have been added, try again: https://web.xyzassociation.org loads without any errors and looks exactly like it always has - with the exception that you are now viewing a secure web page and the browser URL display shows the page as "Secure."
- You notice that most of the direct links and menu items in your website template are hardcoded to use the http version of your URLs, so even though the https version is available and works just fine, no one is actually going to see those secure links. You now have two options:
- Wait for us to enable our automated "redirect" to render all of your http pages in https as soon as any visitor navigates to them. While we don't have a firm date yet, since we need everyone to comply with the above update first, we're hoping this will happen in the next month. OR,
- Update all of your existing website links and menu items to use https instead of http at any time.
Why is this changing?
Click here for more information about DNS and the migration to a secure web.