Layered security reduces unauthorised orders, domain changes and access to support records.
Applies to: Customer Portal access and account security
Customer Portal security protects billing information, services, domains and support history. Use a unique password, keep recovery methods current and treat unexpected sign-in messages as potentially fraudulent until verified.
Before you start
- Sign in as the account owner or an authorised user with permission to manage the relevant details.
- Record the current contact, user or security setting before changing it.
Step-by-step
- Use a unique password stored in a password manager. Do not include the secret in a ticket, email or screenshot.
- Enable two-factor authentication.
- Do not share logins.
- Review users and contacts regularly.
- Treat unexpected payment or domain-change messages as suspicious.
Confirm the result
- The intended account, contact or security setting remains correct after the page is reloaded.
- A new browser session can sign in or use the changed permission without relying on an existing session.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The account detail cannot be edited. | The signed-in user lacks permission, the field is controlled by the account owner, or a verification check is pending. | Confirm the user role and open a secure account ticket when an owner-only or verified change is required. |
| A notification goes to an old address. | The billing account, contact and service-level notification addresses are separate. | Review the account owner and each contact or service notification setting rather than changing only one field. |
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 customer account email address
- The affected invoice, service, domain or ticket number
- The exact message and the time it appeared
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
- Enable two-factor authentication
- Understand account owners, users and contacts
- Recognise a fake Tudor Internet login or payment message
- Recover Customer Portal access when email or two-factor authentication is unavailable
- Reset a forgotten Customer Portal password
Last reviewed: 2026-07-18.
