myxavpn.tech was observed with a CryptoFirewall blocklist entry on 2026-10-13, documenting a relevant security listing for the domain. The domain also achieved a PageSpeed performance score of 96 on the same date, reflecting a technical measurement of its web performance.
Recorded Evidence
On 2026-10-13, CryptoFirewall included myxavpn.tech in its blocklist. The domain was first observed on 2026-10-13. According to VirusTotal, as of 2026-10-11, myxavpn.tech had 0 detections out of 92 total scanners. OTX listed 7 pulses for the domain on 2026-10-13. The registrar recorded for myxavpn.tech is Registrar of Domain Names REG.RU LLC, with a registration date of 2026-06-10. PhishDestroy internally listed the domain as of 2026-10-13.
Interpretation
PhishDestroy provides an internal listing for myxavpn.tech, which records its presence in a security-focused database. VirusTotal's measurement contains the results of automated scanner checks for potential detections, while OTX documents community-sourced intelligence through its pulse count. These sources cover both automated and community-driven security perspectives, offering a broad context for the domain's recorded network profile.
Recommended Actions
To support ongoing assessment, retain the CryptoFirewall blocklist entry and the VirusTotal scanner results for myxavpn.tech. Compare the OTX pulse count and PhishDestroy internal listing to future observations for any changes. Review all recorded evidence for myxavpn.tech periodically to maintain an up-to-date security context.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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.
Google PageSpeed Insights — mobile performance audit of myxavpn.tech· checked Oct 13, 2026
96
Good
Performance
FCP
0.85s
First Contentful Paint
LCP
2.7s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.3s
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-12 23:34:28 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 212.192.14.75.
威胁响应 Pipeline
发现
Analysis
Monitoring
7 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.
黑名单检测
见于 1 blocklist: CryptoFirewall
2026年10月13日
OTX Community References
7 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(SE)
