app-hemi-dashboard.pages.dev returned HTTP status 403 during an HTTP check on 2026-10-01, indicating a restricted or denied response at that time. The domain is also listed in the PhishDestroy internal catalogue, which is a publisher-owned listing.
Recorded Evidence
A VirusTotal scan on 2026-09-17 found 1 detection out of 89 scanners for app-hemi-dashboard.pages.dev. The domain was first observed on 2026-09-04. A PageSpeed check on 2026-09-15 reported a performance score of 99. The SSL certificate scan from 2026-09-15 showed the issuer as Google Trust Services / WE1.
Interpretation
The HTTP status code and VirusTotal detection are independent observations, each reflecting a specific aspect of the domain's recorded activity. The PhishDestroy internal listing provides an additional publisher-specific record, while the PageSpeed and SSL scan results give further technical context. These dated records offer a range of perspectives but do not indicate any direct relationship between the sources.
Recommended Actions
Retain the PhishDestroy listing, VirusTotal scan, and HTTP check records for app-hemi-dashboard.pages.dev as separate references. When reviewing the domain, compare these records to understand the range of observations. Avoid submitting sensitive information to the domain based on the recorded detection and listing.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-15 22:06:51 UTCcurrent episode first observed: 2026-10-01 01:39:30 UTCobserved RIP window: 2026-09-15 22:06:51 UTC → 2026-10-01 01:39:30 UTC · 363.54hmidpoint estimate ≈ 2026-09-23 11:53:10 UTC · precision low · basis bounded
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.
技术 · 3 identified
H
HSTS
安全
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 1 detection
Forcepoint ThreatSeeker
网站性能分析
Google PageSpeed Insights — mobile performance audit of app-hemi-dashboard.pages.dev· checked Sep 15, 2026
99
Good
Performance
FCP
1.68s
First Contentful Paint
LCP
1.68s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.6s
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.
Domain Status Transition2026-09-16 10:00:37 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-14 22:23:13 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
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.
(US)
