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

Start using an approved Non-Profit Hosting service Print

  • hosting, non-profit, siteworx
  • 0

After manual approval, use the normal Customer Portal and SiteWorx workflow and verify the domain, SSL, email and backups before launch.

Applies to: Approved Non-Profit & Club Hosting services

Approved organisations use the standard SiteWorx hosting tools and remain responsible for their content, users, renewals and security. Changes to the organisation may trigger a fresh eligibility review.

Before you start

  • Sign in to the Customer Portal and open the approved hosting service.
  • Take a current backup before changing website files, databases, DNS or application configuration.

Step-by-step

  1. Open the approved service in the Customer Portal and review the activation and renewal dates.
  2. Sign in to SiteWorx through the service link and change any temporary credential.
  3. Upload or migrate the website and test it before changing public DNS.
  4. Point the authorised domain, issue Let’s Encrypt SSL and confirm HTTPS.
  5. Create only the required mailboxes and configure SPF, DKIM and DMARC.
  6. Review backup restore access, SiteLock Lite and 360 Monitoring Lite.
  7. Add authorised organisation users to the portal without sharing the owner login.

Common problems

SymptomLikely causeWhat to do
The application remains under review.Eligibility or authority evidence is incomplete or cannot be verified from the supplied information.Reply with the specific requested evidence and avoid submitting a second application for the same organisation.
The organisation no longer meets the eligibility basis.Its legal status, purpose or control changed after approval.Tell Tudor Internet before renewal so an appropriate standard plan or documented re-review can be arranged without risking data.

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 affected domain and SiteWorx account
  • The exact error text and time
  • The last change made
  • Relevant log lines with passwords 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