mafedex.net was first observed on 2026-10-09, with a recorded entry on the MetaMask blocklist providing a dated security indicator for the domain. The domain also appeared on other external blocklists, which adds context for ongoing monitoring.
Recorded Evidence
On 2026-10-09, mafedex.net was listed on both MetaMask and SEAL external blocklists. VirusTotal checked the domain on the same date, reporting 0 detections from 92 scanners. OTX documented two pulses referencing mafedex.net as of 2026-10-09. PhishDestroy internally listed the domain, and its registration was recorded with Dominet (HK) Limited on 2026-05-05.
Interpretation
PhishDestroy contains an internal listing for mafedex.net, documenting its inclusion in their records and providing a reference point for security intelligence. VirusTotal’s scan-based measurement describes the results from multiple security engines, while OTX records offer additional context through community-driven pulses. The blocklist entries from MetaMask and SEAL represent external security observations relevant for comparison across sources.
Recommended Actions
For mafedex.net, preserve the MetaMask and SEAL blocklist entries to compare with future blocklist records. Retain the VirusTotal scan results and OTX pulse references for subsequent investigations. Review the PhishDestroy listing alongside other source records to maintain a comprehensive evidence history for the domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 22:01:02 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:29:30 UTClast content: 2026-10-13 22:01:02 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.
技术 · 4 identified
V
Vue.js
JavaScript frameworks
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of mafedex.net· checked Oct 9, 2026
56
Needs Work
Performance
FCP
8.72s
First Contentful Paint
LCP
9.64s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
6ms
Total Blocking Time
SI
10.53s
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-09 15:53:46 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.96.1.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(HK)
