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, such as https://secure.mycharity.org. These are set as your Base URL for your pages.
How do I get a subdomain?
- You will need to ensure your HTML template is secure. It is very likely it is already, and all our sample blueprints are secure by default. You can confirm this by checking that your pages’ URLs all start with https:// and that 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 first, make a decision on what subdomain to use – for example secure.yourcharity.com or donate.yourcharity.com. It should be a subdomain and one that is not in use elsewhere.
Then contact Support who will be able to take you through the next steps. As part of this, you will have to make a small 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, and amend individual existing pages’ admin settings.
- You will also need to ensure that any external links to your Engaging Networks pages, such as a Donate button on your homepage, uses the new domain.