Any web page that transfers sensitive data to a server should be protected by a Secure Socket Layer (SSL) certificate. Whenever you see a small padlock on the left-hand side of your browser’s address bar, it tells you that this page is secured by an SSL certificate, and that the data you send from it to a data centre is fully authenticated and encrypted.
This is now a required standard by all major browsers, which is why we provide up to three single domain certificates to all Engaging Networks clients that can be used to protect their Engaging Networks web pages.
By default, you can also use the https://us.engagingnetworks.app or https://ca.engagingnetworks.app subdomains as your Base URLs for pages, but we recommend using your own personalised subdomain, e.g. https://secure.mycharity.org**
- If you are using a secure certificate over https then you will need to ensure your HTML template is secure. It is very likely it is already, but you can confirm this by checking that the pages’ URLs start with https:// and you see the padlock in the browser’s address bar. Any problems please contact Support or see the separate tutorial on setting up https templates.
- If you are using our default domains (https://us.engagingnetworks.app or https://ca.engagingnetworks.app) and wish to use your own subdomain instead (or as well as) then please contact Support who can take you through the process. You will have to make a change to the subdomain, so your IT team may need to be involved.
- Once you have your SSL set up, you can use it as a Base URL in your pages. You can go to the account preferences to make this the default for new pages, or amend individual pages’ admin settings.