A look-alike address
Compare the full domain. Leave a page that imitates a familiar name with extra characters.
Protect access before a problem grows
Account security combines the address you trust, the secrets you protect and the records you keep. Recognise suspicious requests early, then take a specific action instead of continuing under pressure.
Four things worth protecting
- Email access
- Your inbox often receives recovery messages; protect it with its own unique password.
- Passwords
- Use a different long password for each service so one leak does not expose every account.
- Verification codes
- A code can approve a sensitive action. Read its purpose and never forward it to an unsolicited contact.
- Private records
- Keep documents and account screenshots out of ordinary feedback messages.
If you suspect compromise
If the same password was reused elsewhere, change it on those services too.
Stop the interaction
Close the suspicious page or conversation without sending more information or money.
Secure the recovery route
Protect your email, change exposed passwords from a trusted device and review active sessions where available.
Preserve and report
Keep redacted evidence and contact the account operator or payment provider responsible for the incident.
Routine habits reduce exposure
Keep your browser and device updated, and install software from a verified publisher. On shared devices, avoid saving credentials and sign out when finished. A private browsing window can limit local history, but it does not prove that a website is trustworthy.
Separate support evidence from account secrets. A useful report describes the page, time and visible error; it does not need a full account screenshot. Before sharing an image, hide passwords, codes, identity numbers and unrelated financial information.
Know the scope of each route
Login guidance
For rejected credentials or a recovery loop, work through the login sequence.
Read detailsRecord checking
For transaction discrepancies, identify the responsible provider and preserve its reference.
Read detailsPersonal limits
Security controls do not replace time, spending and participation boundaries.
Read detailsPractical security questions
Act on the specific exposure; a suspicious message alone does not require sending more private information to prove ownership.
Does a padlock prove the operator is genuine?
It does not establish the identity or quality of the business. Check the full address and the operator separately.
Should support know my one-time code?
No. Codes can authorise account actions; enter one only in the verified process you initiated.
What makes a screenshot safer to share?
Crop to the relevant error and hide credentials, identity details, account numbers and unrelated balances.
What if I already shared a password?
Change it from a trusted device, secure the recovery email and replace any reused version elsewhere.
Report without exposing secrets
Related guidance
Describe the suspicious request and hide passwords, codes and identifying account information.
Email about this page
Send the page address and a focused question to [email protected]; leave private account information out.
Continue
Use a verified recovery route
The login page explains recovery stages; the privacy page helps you limit information in a report.