Security engines reporting a detection: 6. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
The domain faran.ac.ir was observed in a recorded snapshot on 2026-10-13, with a notable entry on the OpenPhish blocklist. Additionally, the domain achieved a PageSpeed performance score of 92, reflecting a measurement of its technical infrastructure.
Recorded Evidence
OpenPhish listed faran.ac.ir on 2026-10-13, marking it as an entry in its external blocklist. VirusTotal checked the domain on the same date, documenting 6 detections out of 92 total scanners. OTX pulses were recorded at 50 during its 2026-10-13 check. The SSL certificate for faran.ac.ir was issued by Let's Encrypt / YR1, with its status scanned on 2026-10-13.
Interpretation
PhishDestroy contains an internal listing for faran.ac.ir, which records its presence in a monitored environment. VirusTotal provides a quantitative assessment of detections from multiple scanners, offering a broad perspective on network security observations. The evidence from these sources covers both external and internal monitoring, allowing for comparison of technical and security-related records.
Recommended Actions
To maintain a comprehensive review of faran.ac.ir, preserve the OpenPhish blocklist entry and VirusTotal detection record for future comparison. Retain OTX pulse counts and PhishDestroy internal listings as reference points for ongoing security assessments. These records can be used to track changes and inform subsequent technical reviews of the domain.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Certificate hostname mismatch·
Issued by Let's Encrypt / YR1· stored validity ends in 37 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
94.182.163.148
Nameservers 4
d.ns.arvancdn.ir
ns1.faranlms.ir
ns2.faranlms.ir
x.ns.arvancdn.ir
Mail routing 1 MX record
mail.faran.ac.irpriority 10
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR1
Valid from
2026-08-21 15:43:18
Valid until
2026-11-19 15:43:17
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-13 04:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7ffde7af53614ccba15fba308f2e910b4de4f78d09cd369da4c2d6459fb1d52cCertificate names · 7 SANs
hamayesh.faran.ac.ir
library.faran.ac.ir
reg.faran.ac.ir
res.faran.ac.ir
stu.faran.ac.ir
teach.faran.ac.ir
www.faran.ac.ir
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 03:49:57 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 03:49:57 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed Previous stored snapshot: 6 detections
ADMINUSLabs
alphaMountain.ai
DNS8
Fortinet
Gridinsoft
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of faran.ac.ir· checked Oct 13, 2026
92
Good
Performance
FCP
0.91s
First Contentful Paint
LCP
2.12s
Largest Contentful Paint
CLS
0.105
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
5.38s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-13 03:44:54 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 94.182.163.148.
Threat Response Pipeline
Discovery
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
5 evidence signal groups linked0 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
