An eligible SiteLock firewall service sits in the website traffic path. Prepare the origin, HTTPS and DNS change together so visitors continue reaching the correct application while the firewall is activated.
IN THIS ARTICLE
01 Prepare a controlled change
Confirm that Firewall & CDN is included in your order. Record the existing website DNS answers, origin address, certificate coverage and any current proxy. Arrange access to the authoritative DNS manager and a person who can test the hosting server.
02 Activate and verify
- Open the site's Setup Wizard > Firewall Activation. Complete any ownership and certificate stages requested for this hostname.
- Confirm that the configured origin is the actual hosting endpoint. Check that its application works before routing customers through a new intermediary.
- Apply only the DNS changes displayed for the ready activation stage. Preserve unrelated mail and verification records.
- Test the public HTTPS site from a separate connection. Exercise login, search, forms and checkout, including callbacks or integrations used by the business.
- Review caching before enabling aggressive options. Private account pages, personalised responses and checkout need application-appropriate handling.
- Record the previous routing values and a recovery contact. Keep both the origin and the security subscription available until verification is complete.
Common questions
Can I leave another proxy in front of SiteLock?
Do not assume two security proxies will work together correctly. Confirm the supported routing with both providers, including source addresses, certificate handling and cache behaviour, before combining them.
Will changing DNS move my files?
No. The origin still serves the application. A wrong origin address can send visitors to the wrong site even when the public DNS update is correct.
What if the homepage works but checkout fails?
Capture the failing URL, time and error reference. Check firewall events, application logs and cache behaviour for that action. Avoid disabling all protection before identifying the specific rule or configuration problem.