metks.vip was recorded on the MetaMask blocklist as of 2026-10-13, and its network performance was measured with a PageSpeed score of 91 on the same date. The domain was also observed in multiple security intelligence sources, providing a range of technical and security-related data.
Recorded Evidence
On 2026-10-13, metks.vip appeared on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on 2026-09-29, recording 6 detections out of 92 total scanners. PhishDestroy internally listed the domain, and its registration date is documented as 2026-09-27. A PageSpeed performance score of 91 was measured on 2026-10-13.
Interpretation
The VirusTotal record contains a quantitative measurement of how many security scanners flagged metks.vip, offering insight into its detection by industry tools. The PhishDestroy listing documents an internal assessment, while the MetaMask and SEAL blocklist entries show the domain’s inclusion in external security databases. These records collectively provide a multi-source snapshot of how metks.vip was evaluated across different platforms and dates.
Recommended Actions
For metks.vip, retain the VirusTotal detection record and the PhishDestroy internal listing for future reference and comparison. Keep documentation of the MetaMask and SEAL blocklist entries to track any changes in external security status. Use the PageSpeed performance measurement as a technical baseline for monitoring the domain’s infrastructure over time.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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 metks.vip· checked Oct 13, 2026
91
Good
Performance
FCP
2.24s
First Contentful Paint
LCP
2.33s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
54ms
Total Blocking Time
SI
5.73s
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:43:00 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 47.76.139.211.
위협 대응 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.
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)
