Account safety: pause and check

A warning is a claim to check

An unexpected message says your project will disappear unless you send a sign-in code. It uses a familiar display name and sounds urgent. That is a claim, not proof. We will practice choosing a safer next step using an invented message. There is no real link, attachment or code to try.

Choose a route you already trust

Do not send the code or open the unexpected attachment to investigate it. Ask a trusted adult and check through an established contact or the official app you already know. A familiar display name can be copied. Good spelling and a polished design do not turn an unexpected request into a trustworthy one.

Avoid reusing the same password

Now imagine accounts A and B reuse one secret while account C has a different one. If the reused password is exposed, it may be tried on both A and B. A reputable password manager can help create and store strong, different passwords. Arrange setup and recovery with a trusted adult, not inside a worksheet.

An extra check has its own job

Multifactor authentication adds another kind of proof when signing in. Two passwords alone are still the same kind of factor: something you know. If a sign-in approval appears when you did not start signing in, do not approve it to make it go away. Get help through an official route and keep recovery codes private.

Pause: the friendly-looking request

Here is a fresh request with a friendly name and perfect spelling. It asks you to send a sign-in code to confirm your school project. You did not start a sign-in. Pause and choose between sending the code or keeping it private while checking through a route you already trust. Explain which detail actually matters.

A familiar label is not proof

Choose B. Keep the code private and check separately with help from a trusted adult. Neither the friendly label nor correct spelling proves who sent the message. If you already responded, tell a trusted adult promptly and use the service's official recovery help. Getting help is more useful than hiding a mistake.

Two passwords are not two factors

Fun fact: asking for two different passwords does not, by itself, create two different authentication factors. Both are things you know. Another factor adds a different kind of proof. These ideas help explain the controls, but no single feature makes an account invincible. Careful choices and a recovery plan still matter.

Continue with fictional messages

Continue to the worksheet below. Choose a safer response to the invented warning and explain why opening an attachment is not a safety test. Then try Keep Account Protections Separate. Use only the fictional labels printed there. Do not enter a real password, sign-in code, recovery code or private account detail.