Emergency Preparedness
Preparedness starts with a plan—and knowing who you can trust.
This Disaster Healthcare Coalition training scenario demonstrates how a familiar-looking page can make an unexpected request feel credible. Appearance is not proof of identity.
HANDS-ON TRAINING
Emergency preparedness verification
Practice reviewing a verification request. Use fictional sample information only—never your own details or those of an emergency contact.
The private collection service is pending approved deployment. This exercise currently runs only in your browser.
Pause before you share.
This sample was not saved or sent. On a malicious site, a similar form could disclose your contact details and someone else’s address.
Look at the address bar: ph.mondolmedia.com is not countyofsb.org. A padlock means the connection is encrypted—not that the organization is legitimate.
Review the protective steps belowBefore you trust a QR code
- Preview the destination. Read the full hostname before opening the link. Watch for misspellings, lookalike domains, and shortened URLs.
- Use a trusted route. Open the organization’s saved website or type its known address yourself. Don’t rely on the QR code to verify itself.
- Question the request. Urgency, personal-information demands, payments, and sign-in prompts deserve an independent check.
- If you shared information, act. Stop interacting, notify your security team, and change any exposed password through the real website. Never approve unexpected MFA requests.
Trusted resources
The links below leave this simulation and open the real organizations’ websites.