VirusTotal
0 / 92 engine detections
レポートを開く“Проверка — PRODARK”
prodark1.net — 最後に確認されたアクティブな状態 (HTTP 302). 証拠の概要: VirusTotal 0/92; PhishDestroy score 73/100. レジストラ: TUCOWS.COM, CO.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
0 / 92 engine detections
レポートを開くScan report
レポートを開く3 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
prodark1.net appeared on the PhishDestroy blocklist on 2026-10-19. The site is currently alive but its content could not be retrieved during the last check on the same day. It was registered on 2026-07-08 and shows no obvious branding, suggesting it may be used to impersonate a cryptocurrency service and target crypto‑wallet owners. PhishDestroy’s first sighting aligns with the domain’s recent registration, indicating a short window before detection.
Although the page title is unavailable, the classification as a suspicious domain implies a typical phishing or wallet‑drainer approach. Victims are lured to a fake interface that asks for private keys, seed phrases, or wallet connection approvals. Once entered, attackers can move funds out of the victim’s wallet or steal credentials for later unauthorized access. The loss is usually the total balance of the compromised wallet.
VirusTotal scanned the domain with 92 engines and reported 0 detections, indicating the site itself may not host known malware but still poses a social‑engineering risk. OTX lists three pulses referencing prodark1.net, and PhishDestroy has added it to its blocklist. No other major blocklists or Google Safe Browsing alerts were found at the time of review.
The domain was registered on 2026-07-08 through TUCOWS.COM, CO., a common registrar for short‑lived malicious sites. Hosting resolves to IP 104.21.42.97, which belongs to a large content‑delivery network often used to hide the true origin of malicious traffic. The registration‑to‑detection interval of roughly three months suggests a rapid deployment and takedown cycle.
Anyone who visited prodark1.net should immediately disconnect any linked wallets, revoke all pending approvals, and change passwords on associated accounts. Enable two‑factor authentication wherever possible and monitor blockchain addresses for unexpected activity. Security teams should block the domain at DNS and proxy layers, add it to internal threat intel feeds, and watch for newly registered domains using the same registrar or hosting provider.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/VhodTutLink_botStored page referenceIoC extraction recorded 2026-10-20 04:00:08 UTC
Edge-IP の評判はこのドメインに起因しません。
grace.ns.cloudflare.commajor.ns.cloudflare.comLocation describes the IP network.
7d2e7899f4fa16d1cd21541b0e91f22aec7b869f39d6b7f98b15609a10799038Saved 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.prodark1.netDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of prodark1.net · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://prodark1.net/https://prodark1.net/preloaderContent-Type: text/html; charset=utf-8Server: cloudflareCache-Control: no-cacheCF-Cache-Status: DYNAMICContent-Encoding: gzip9be0d5fc1c3533d7c746d7d580689e737051c582d9d44a7895de8bbe8f235e12truehttps://prodark.neth3=":443"; ma=86400no-cacheDYNAMICa4cfca297cabf2bc-YYZkeep-aliveinline; filename=CaptchaPage.htmlgziptext/html; charset=utf-8same-originsame-originMon, 19 Oct 2026 12:29:40 GMTSat, 08 Aug 2026 15:12:42 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}camera=(), microphone=(), geolocation=()strict-origin-when-cross-origin{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=mFUFNMDe6214IC8499EVkJbFJiv9x8KPp%2Bb6vEAxnXYeW%2FFKwiQtZaz5CuArCdrou5jKvRcCclAjGXPpRx5aKeuMTtsR6UWILO6RjlTWT%2BSHPZsaucN7MUmbMoOpszA%3D"}]}cloudflarecfCacheStatus;desc="DYNAMIC"chunkedOriginnosniffDENYValues retained by the collector; long values may be shortened during collection.
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_302; http=302; via=https_proxy; location=/preloader?next=/; server=cloudflare
prodark1.net
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
利用不可→到達可能
到達可能→利用不可
到達可能
3 community references
View sourceNo threat flag
View source0/92 engine detections
View sourcePD-20261019-CD4BE1
prodark1.net
View sourcePage captured
View sourcePD-20261019-CD4BE1 Recipient: domainabuse@tucows.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
prodark1.net)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.