VirusTotal
4 / 91 engine detections
レポートを開く“Login | Vid-Pro”
Security analysis of vidpro.online covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 91 engine detections
レポートを開く3/14
checked — no detections recorded
レポートを開くchecked — no match recorded
23 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
vidpro.online was registered on March 03, 2026 through NameCheap, Inc. and currently resolves to 172.67.149.250, an address owned by Cloudflare, Inc. The site is live and returns HTTP 403 for direct requests, but presents a login page titled “Login | Vid‑Pro”. The page mimics the Telegram brand, indicating a deliberate impersonation campaign targeting Telegram users. Risk level is classified as high and the domain is listed as active. The hosting environment is built on PHP and includes reCAPTCHA, Hostinger branding, Cloudflare Browser Insights, and HTTP/3 transport, all delivered behind Cloudflare’s edge network. DNS is served by elliot.ns.cloudflare.com and ziggy.ns.cloudflare.com, and the site uses a Let’s Encrypt certificate (E7). Reputation services assign a Gridinsoft trust score of 0 / 100, and the domain appears on one security blocklist. VirusTotal records a single positive detection out of 95 scanners. Technical analysis points to a classic brand‑impersonation kit that harvests credentials via a forged Telegram login interface. The presence of reCAPTCHA suggests an attempt to bypass automated detection, while the PHP backend likely forwards submitted credentials to an attacker‑controlled endpoint. No additional malicious payloads are observable from the landing page, and the underlying phishing kit remains unidentified. The short lifespan of the domain (registered only four months ago) aligns with fast‑flux deployment practices. Defenders should add vidpro.online to outbound web‑filter deny lists and incorporate the IP address 172.67.149.250 into network‑level block rules, acknowledging that Cloudflare may host multiple unrelated sites. Email gateways should flag messages containing URLs or shortened links that resolve to this domain. Continuous monitoring of DNS queries for the domain and its nameservers is advised, and security awareness training should remind users that legitimate Telegram authentication never occurs on third‑party domains.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/vidpro_customer_serviceStored page referenceIoC extraction recorded 2026-07-29 02:27:23 UTC
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.
Edge-IP の評判はこのドメインに起因しません。
ziggy.ns.cloudflare.comLocation describes the IP network.
cf0a6d3268b969f29fed880c110399447e26dd29bcbdd7e09cdc6cb16a3983f7Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of vidpro.online · checked Mar 4, 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.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://vidpro.online/; server=cloudflare
vidpro.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
利用不可→到達可能
到達可能→利用不可
1→3
https://radar.cloudflare.com/scan/7f595508-169f-4f3c-a313-e9576694291e
No threat flag
View source4/91 engine detections
View source23 community references
View sourcePage captured
View sourcevidpro.online
View sourceコミュニティの 1 人が報告・初回確認 2026年3月3日
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
vidpro.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.