The domain mew-io.pages.dev returned an HTTP 403 status on 2026-10-03, indicating restricted access at that time. Additionally, it has been flagged by Google Safe Browsing for social engineering threats, suggesting potential risks to visitors.
Recorded Evidence
On 2026-09-17, Google Safe Browsing identified mew-io.pages.dev as a source of social engineering threats. The domain was also checked by VirusTotal on the same date, with 2 detections out of 89 scanners. As of 2026-10-03, the HTTP response was 403. The domain appeared in the PhishDestroy internal listing as of the latest review. A PageSpeed performance score of 97 was recorded on 2026-09-15.
Interpretation
These source records provide insight into both the security and accessibility of mew-io.pages.dev. The Google Safe Browsing flag highlights a specific threat category, while the HTTP 403 response suggests that access was restricted or denied at the time of testing. VirusTotal's multiple detections further indicate that at least some security vendors have identified issues with the domain. The presence in the PhishDestroy internal listing means it is being tracked by that publisher's system.
Recommended Actions
Review the evidence for mew-io.pages.dev from Google Safe Browsing, VirusTotal, and HTTP response records to assess potential risks. Preserve the exact threat categories, detection counts, and HTTP status codes for future comparison. Monitor these sources for any updates or changes in their assessments of the domain.
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-05 04:28:18 UTCcurrent episode first observed: 2026-10-01 01:39:22 UTCobserved RIP window: 2026-09-05 04:28:18 UTC → 2026-10-01 01:39:22 UTC · 621.18hmidpoint estimate ≈ 2026-09-18 03:03:50 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: 2 detections
alphaMountain.ai
LevelBlue
网站性能分析
Google PageSpeed Insights — mobile performance audit of mew-io.pages.dev· checked Sep 15, 2026
97
Good
Performance
FCP
1.53s
First Contentful Paint
LCP
2.18s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.82s
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.
Status Check2026-09-16 19:38:14 UTC
Telemetry event observed.
VirusTotal Detections Update2026-09-16 19:37:52 UTC
VirusTotal scanner detections updated from 0 to 2. Added scanner alerts: LevelBlue, alphaMountain.ai.
Domain Status Transition2026-09-15 10:00:18 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 03:23:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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)
