Before you start
Use a trusted device and open university services from their official addresses. Never enter a password or code into this guide.
Actions for your situation
I received a message
- If you only received a message, treat urgent account threats, requests for passwords or codes, unexpected attachments, and lookalike domains as reasons to check further. These signs alone do not prove phishing.
- Do not open suspicious links or attachments or reply. Visit the university service from an official source you open yourself, or check the message through an official IT Center contact.
- Check the full address before signing in. The university identity portal uses auth.ilam.ac.ir. A padlock or HTTPS alone cannot establish that a lookalike domain is genuine.
I opened a link or downloaded or ran a file
- If you opened a link but entered nothing, close the page and do not download or run anything. Note the time, address and message for a report. Opening a link alone does not establish that your password was stolen.
- If you only downloaded an unknown file, do not open or run it; ask the IT Center how to remove it safely. If you opened or ran it, avoid sensitive sign-ins on that device and promptly ask the IT Center to assess it. Report any signs of infection or unexpected installation prompts.
I entered or shared credentials
- If you entered a password or code, open the official portal yourself on a trusted device and change your password. Do not approve an unexpected sign-in request; ask the IT Center to check your sign-in methods and active sessions.
- If you exposed recovery codes, an authenticator QR code or a personal certificate file, say so in the report so those access methods can be reviewed and replaced if necessary.
Report the incident
- Report promptly through the university's official support route with the time, sender, suspicious address and action taken. Never send passwords, current codes, QR codes or certificate files. A dedicated phishing address has not been verified.
After these actions
The next step depends on what you did. Changing a password alone does not complete incident response if a file ran or an access method was exposed. Contact the IT Center.
Report or ask for help
The university IT Center lists these as general contact details. A dedicated incident channel has not been verified.
Email opens a draft; you must send it yourself. This guide does not submit an incident report. Never send passwords, codes or certificate files. Official contact source ↗
If the issue persists
Try the troubleshooting path, then prepare the error text without passwords or codes.
Contact the IT CenterStill need help?
Prepare the service name, error message and steps you have tried. Do not send passwords or sign-in codes.
Sources and review status
Last text review: 3 October 2026
Editorial responsibility: Supplementary guide editorial team · University technical approval: not received; technical owner not designated
Next planned review: 2 November 2026
Account and authentication guide ↗ · CISA guidance on recognizing and responding to phishing ↗
A university source link does not establish that all settings and policies are current.
Use your browser’s Print option to print or save a PDF. To share, copy this page’s address.