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

Why a Non-Profit Hosting application is pending Print

  • hosting, non-profit, verification, support
  • 0

Manual review may pause an order while Tudor Internet confirms the organisation, intended use or applicant authority.

Applies to: Non-Profit & Club Hosting applications

Non-Profit & Club Hosting is intended for eligible clubs, CICs, associations and community organisations operating for member or community benefit rather than private profit. Applications are manually reviewed.

Before you start

  • Have the organisation's legal or commonly used name and an authorised contact available.
  • Prepare the evidence requested for manual eligibility review, with unnecessary personal data redacted.

Step-by-step

  1. Open the related Customer Portal ticket and identify the exact missing or inconsistent information.
  2. Reply in the same case rather than submitting another order.
  3. Provide current evidence and explain unusual organisation structures or trading names clearly.
  4. Confirm that the intended website and email use fits normal shared-hosting and non-profit-plan restrictions.
  5. Wait for approval before changing DNS or cancelling an existing host.
  6. If the application is declined, use a standard hosting plan where the intended use remains permitted.

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