VirusTotal
6 / 91 engine detections
レポートを開く“Zoom - Meeting Invitation”
Zoomなりすまし: zoomeetingvideo.online — コンテンツが利用できません. 証拠の概要: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); URLQuery 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 91 engine detections
レポートを開く2 threat-system alerts
レポートを開くDBL_PHISH
no community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| YARAhub by abuse.ch | zoomeetingvideo.online/ |
malware | Detects file containing Telegram Bot API |
| Hagezi Threat Feed | zoomeetingvideo.online |
malicious | Sinkholed |
PhishDestroy threat report
Analysis of zoomeetingvideo.online, created on July 20, 2026 and registered through Spaceship, Inc., shows a newly provisioned domain that is currently active. The domain resolves to the IPv4 address 31.177.109.168 and is served by Cloudflare nameservers (bethany.ns.cloudflare.com and langston.ns.cloudflare.com). Independent blocklist services have already listed the domain: PhishDestroy, MetaMask, and SEAL have each blocked it, and it appears on three additional security blocklists, indicating that multiple threat intelligence feeds consider it malicious.
VirusTotal has scanned the domain with 91 antivirus and URL‑reputation vendors; none of the scanners reported a detection at the time of the scan. While a zero‑detection count does not constitute evidence of safety, it does confirm that the domain has not yet been flagged by the vendors participating in that particular scan. The combination of recent registration, active status, association with known blocklists, and the lack of any benign reputation signals points to a high‑risk profile consistent with the generic phishing classification provided.
Defenders should treat the domain as hostile: network perimeter controls should deny outbound connections to the IP address 31.177.109.168, DNS filtering should block queries for zoomeetingvideo.online, and endpoint security policies should include the domain in block lists. Continuous monitoring of threat‑intel feeds for any new indicators, such as changes in hosting, SSL certificate issuance, or observed payloads, is recommended to maintain situational awareness.
Last checked
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.
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.
bethany.ns.cloudflare.comlangston.ns.cloudflare.comroute3.mx.cloudflare.netpriority 2route2.mx.cloudflare.netpriority 8route1.mx.cloudflare.netpriority 74Location describes the IP network.
d9ede7edfb9955d4a0be307cc91c0fbef5e03386f34bdc5ac0d6875152347e4bwww.zoomeetingvideo.onlineSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.zoomeetingvideo.onlineDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of zoomeetingvideo.online · checked Jul 22, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
zoomeetingvideo.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
6/91 engine detections
View sourcePD-20260722-74AF53
No threat flag
View sourcezoomeetingvideo.online
View sourcePage captured
View sourcePD-20260722-74AF53 Recipient: abuse@smartape.ru アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
zoomeetingvideo.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.