Check independently
Navigate through an already verified address rather than an unsolicited link. Compare the full sender domain and destination hostname. A brand logo, a display name or a secure-connection icon does not authenticate the person sending a message.
Do not expose account access
Never send a password, recovery phrase or one-time authentication code to someone claiming to be support. Be especially cautious of requests to install remote-access software or pay a release fee into a personal wallet.
Keep evidence
Save the message and its visible sender details without opening unexpected attachments. If an account may be compromised, use the service's verified security route and your payment provider's official contact channel. A public review site cannot recover an account on your behalf.
Quick checklist
- Verify the domain
- Keep codes private
- Do not install unsolicited tools
- Save the message
Sources & scope
Primary documents are linked below. Operator statements and independently checked records are different kinds of evidence.
Source review: 5 November 2026. Links can change. No transaction or customer-support test is implied.
About this explanation
Numerical examples are hypothetical unless a source is expressly identified. This page does not recommend an operator or promise an outcome. The UK regulator references explain technical terms; they are not Australian legal guidance.
Research method · Flag an issue
National self-exclusion register ↗
Independent support information ↗