Lesson 3 of 23 · About 4 minutes

Pause before the click

Read the request.

Phishing uses a message to push you toward an unsafe action. A familiar name or polished design is not proof that a request is trustworthy.

Look beyond the display name

Check the actual sender and destination, not just the logo or the words on a button.

Notice the pressure

Threats, urgency, and unexpected requests for sensitive information are reasons to slow down.

Verify independently

Open a known app or use a trusted contact method instead of a link or number supplied in the message.

A friend’s account can send an unsafe link

“Is this you in this video?” creates curiosity and pressure. If it leads to an unexpected sign-in page, stop. Call the friend using a number you already know and open the real app yourself. A familiar account might be compromised; the message alone does not mean your device is infected.

Recover through the real service

If you entered a password, open the real service independently, change that password and any reused copies, review active sessions, and enable stronger sign-in protection. Report the suspicious message using the app’s controls. If you installed software or see signs of compromise, get trusted help with the device too.

Field example03 / A

“Is this you in this video?”

In Day 28, a message from Max promises a video but sends Leo to a page asking for his password. Leo calls Max instead. The Day 31 recap applies the same habit to a free-candy lure and an urgent payment demand: pause, open the real app, and verify before sharing information or paying.

SEE THE IDEA

Read past the familiar name

Fictional email to a learner at acme.example.

  1. Display name
    IT Support

    A name or logo can be copied.

  2. Actual sender
    help@acme-reset.example

    A different domain deserves scrutiny.

  3. Pressure
    Your account closes in 15 minutes

    Urgency pushes you to skip verification.

  4. Displayed destination
    acme-reset.example/verify

    Use the known portal instead. This example is not a link.

These clues justify a pause and independent verification. They do not require opening the destination.
Read the visualWhere should you verify the request?

Use a known app, bookmark, or trusted IT contact. The suspicious message should not supply its own proof.

Investigate the inbox.

Explore the practice space, then answer the check-in below. A correct answer lets you save this lesson to your progress.

INTERACTIVE VISUAL · FICTIONAL PRACTICE

Inspect the message. Verify the request.

Look behind the sender name, preview the destination without opening it, and check a saved account portal before deciding what to do.

Enable JavaScript to use the diagram controls. No real accounts or files are accessed. The illustrated explanation and recap remain available without JavaScript.

A safer next move.

Pause, verify through a trusted route, and report suspicious messages.

  1. Pause

    Give yourself time to check the sender, destination, and request.

  2. Verify

    Open a known app, use a saved bookmark, or call a trusted number.

  3. Report

    Use your email provider’s report control or follow your workplace process.

YOUR LEARNING SPACE