Request a Sample

Latest Mailing Database

How to Recognise Phishing Without Trusting the Display Name

A familiar display name or convincing logo does not establish who sent an email. If a message asks for money, passwords, a sign-in code or an unexpected document download, pause and verify the request through a separate route you already trust.

Check the request before the design

Consider whether you expected the message and whether the action makes sense. Urgency, pressure to bypass normal approval or an unusual change in payment details deserves further checking. Good spelling does not prove authenticity, and an error is not the only sign of a suspicious message.

Use a separate trusted contact route

Open the organisation’s app or type its known website address yourself rather than using an unexpected login link. For a work request, use your established internal contact channel. Do not reply to a suspicious message or call the number inside it merely to ask whether it is genuine.

Understand email authentication

Gmail provides details about message authentication, including mailed-by and signed-by information. Authentication can help assess sending-domain claims; it does not establish that every authenticated message is safe. A compromised account or a misleading lookalike domain can still send harmful content. Treat headers as one part of the review.

Report and contain the problem

Use your organisation’s reporting process or the email service’s phishing control. Preserve the message for the responsible security team when instructed. If you entered credentials or approved a suspicious action, contact the legitimate organisation or your security team through a trusted channel and follow their recovery steps. NIST provides guidance on recognising phishing and responding to it.

References

Scroll to Top