Skip to content

Knowledgebase

Removing an obsolete SiteLock integration carefully

security-ssl

Remove an obsolete SiteLock integration in the right order. A website that still routes through a cancelled security service can stop working, even when its hosting account and files remain available.

01 Prepare and remove the dependency

  1. Identify everything the subscription supplies: scanning, cleanup, firewall routing, certificates, caching, a trust seal or other purchased features. Record which replacements are required.
  2. Export the security reports and incident records that your business needs. Confirm any retention requirements before closing access.
  3. For a site using the firewall, prepare the supported replacement route and its HTTPS certificates. Check that the destination works with the intended hostnames.
  4. Change only the relevant website routing records through the authoritative DNS manager. Allow existing cached answers to expire and verify traffic from more than one network.
  5. Test login, forms, checkout and integrations on the replacement route. Confirm that origin firewall restrictions are appropriate for the new architecture.
  6. Remove the obsolete trust-seal code and unused integration components. Revoke credentials or keys that were dedicated to the retired service after its final work is complete.
  7. Request cancellation through the current Nabtech account process once the operational dependency is removed. Record the effective date and final billing status.

Common questions

Does uninstalling a plugin cancel the subscription?

Do not assume so. Website code, traffic routing and the commercial subscription are separate items. Confirm cancellation in the service account.

Can I just delete all SiteLock DNS records?

No. First identify the correct replacement for each active website record. Preserve unrelated DNS entries and any verification still required by another service.

What if the site is already showing a proxy error after cancellation?

Provide the domain, current DNS answers and error reference to support. Restore an approved working route and certificate configuration rather than repeatedly reinstalling the website.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support