Account security · QUICK REFERENCE
Checking an unexpected support message
Unexpected contact deserves an identity check before you share account information. Use a previously established support route rather than links or phone numbers supplied by the new message. Keep a copy of the message so you can report the impersonation attempt if appropriate.
A practical checklist
- Check the sender's full address.
- Open the known support channel independently.
- Do not send passwords or one-time codes.
Putting it in context
A message may use a correct logo and mention a real case reference. Those details do not independently authenticate the sender or the destination of its link.
Keep in mind
This guidance concerns suspicious contact, not verification of a particular operator's service.
References & further reading
The checklist and examples are original editorial guidance. External links provide background within their stated scope; they do not validate an individual operator or case.
- NCSC: staying secure onlineUnited Kingdom · account-security guidance
- NCSC: phishing guidanceUnited Kingdom · suspicious-message guidance
About this edition: how the content is made · corrections & limitations