Charity Hosting does not include a free domain promotion; register, transfer or point an authorised domain separately.
Applies to: Approved Charity Hosting services
Once approved, Charity Hosting is managed through the same SiteWorx platform as standard hosting. The discounted status does not remove normal security, acceptable-use, renewal or data-protection responsibilities.
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
- Confirm who legally controls the domain and that the charity authorises its use.
- Register or transfer the domain separately, or keep it with the current registrar and change only DNS.
- Point the domain to the hosting service after the website and mail plan are ready.
- Issue Let’s Encrypt SSL and verify HTTPS before publishing the new address.
- Configure SPF, DKIM and DMARC for any hosted mailboxes.
- Keep domain renewal active independently of the hosting renewal and ensure more than one authorised person receives expiry notices.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Some networks show the new result while others show the old one. | Recursive DNS caches have not expired or authoritative nameservers do not return consistent data. | Check the authoritative answer first, compare all listed nameservers and wait for the previous TTL before making another change. |
| The domain returns NXDOMAIN or SERVFAIL. | The zone is missing, delegation is wrong, DNSSEC is broken or an authoritative server is not responding. | Verify delegation at the registry, confirm the zone exists on every authoritative server and remove stale DS records only through a controlled DNSSEC rollback. |
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
- Register a new domain name
- Change a domain’s nameservers
- Enable a free Let’s Encrypt SSL certificate
- Set up SPF, DKIM and DMARC records
- Renew Charity Hosting and maintain eligibility
Last reviewed: 2026-07-18.
