Skip to content
UK web hosting, domain names, email, website security and online services.

Use the SiteLock trust seal Print

  • sitelock
  • 0

Eligible plans can display a SiteLock seal after the site is configured and scanned.

Applies to: SiteLock website security

SiteLock plans provide website scanning and security services. SiteLock Lite is included with Tudor Internet hosting products; paid SiteLock tiers can add capabilities depending on the selected plan.

Before you start

  • Confirm the active product or addon and the domain or user it protects.
  • Record the current settings before changing them.

Step-by-step

  1. Obtain the current embed code from the SiteLock portal. Do not include the secret in a ticket, email or screenshot.
  2. Add it to the website theme or approved content block.
  3. Clear caches and test.
  4. Remove the seal if the subscription ends or the terms no longer permit display. Read the confirmation text because the action may remove data or interrupt service.

Confirm the result

  • The service dashboard shows the intended setting or activation state after reload.
  • A live test from a separate session or device confirms that the customer-facing service works as expected.

Common problems

SymptomLikely causeWhat to do
The service does not show as active in its dashboard.Provisioning is pending, the wrong plan is selected or the service requires an additional activation step.Check the Customer Portal service status and order email, then open a ticket with the service ID instead of creating a duplicate order.
The dashboard setting is correct but the public result is not.DNS caching, an integration token, a device cache or a second service layer still uses the old value.Test from a separate session, check the integration and record exact timestamps before changing the setting again.

When to contact Tudor Internet

Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:

  • The addon service and protected domain or user
  • The plan or licence level
  • The time the issue started and exact message
  • Screenshots with credentials, tokens and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.

Related articles

Last reviewed: 2026-07-18.


Was this answer helpful?

« Back