The domain ovpzr.com returned an HTTP status 200 on 2026-10-12, which documents a successful response recorded on that date. On the same day, it was noted on two external blocklists, MetaMask and SEAL, indicating its presence in security monitoring records.
Recorded Evidence
VirusTotal recorded 5 detections out of 92 scanners for ovpzr.com as of 2026-10-11. The domain was first observed on 2026-10-11 and registered with Dynadot Inc on 2025-12-07. OTX documented four pulses for this domain on 2026-10-12. PhishDestroy internally listed the domain, and the SSL certificate was issued by Let's Encrypt / YR1, as scanned on 2026-10-12.
Interpretation
The PhishDestroy internal listing contains a record of ovpzr.com, reflecting its inclusion in a specialized monitoring database. VirusTotal provides a measurement of detections across multiple scanners, offering a comparative technical perspective. OTX records add further context by documenting community-driven security observations, and the HTTP status code captures a dated response from the domain's web server.
Recommended Actions
For ovpzr.com, preserve the VirusTotal, OTX, and PhishDestroy source records for ongoing comparison. Review the external blocklist entries from MetaMask and SEAL to track any changes in its listing status. Use the HTTP status and SSL certificate records to monitor technical changes over time.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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-12 10:00:29 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-12 10:00:29 UTClast content: 2026-10-12 10:00:29 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.
기술 · 3 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.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
LevelBlue
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of ovpzr.com· checked Oct 12, 2026
61
Needs Work
Performance
FCP
2.99s
First Contentful Paint
LCP
10.81s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
15ms
Total Blocking Time
SI
9.85s
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 09:38:11 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 202.146.222.88.
위협 대응 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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)
