VirusTotal
11 / 91 engine detections
レポートを開く“Home | Telcoin”
フィッシング: vote-telcoin.network — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 11/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 91 engine detections
レポートを開くSuspicious
レポートを開くchecked — no match recorded
no community references
レポートを開く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
The domain vote-telcoin.network was registered on March 5 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com. It resolves to 104.21.20.87, an address owned by AS13335 Cloudflare, Inc., located in the United States. The site is protected by Cloudflare and serves HTTP/3 traffic, but the only observed HTTP response is a 403 status code, indicating that the content is currently inaccessible. A Let's Encrypt certificate (E7) is present, confirming TLS termination at the edge provider. The page title returned from the server reads “Home | Telcoin”, suggesting an attempt to reference the Telcoin brand, and the listed scam type is “Wallet/Seed Phishing”.
The domain has been added to three public blocklists and is actively blocked by security products PhishDestroy, MetaMask, and SEAL. Reputation scoring is extremely low, with Gridinsoft assigning a trust score of 0 out of 100. VirusTotal analysis shows that one of ninety‑four scanning engines flagged the domain, reinforcing the suspicion of malicious intent. Nameserver records point to dilbert.ns.cloudflare.com and georgia.ns.cloudflare.com, both standard Cloudflare resolvers.
Because the site is currently offline, direct payload inspection is not possible, and the exact phishing page layout remains unknown. However, the combination of brand‑targeted page title, wallet/seed phishing classification, low trust score, blocklist presence, and a flagged detection provides strong evidence that the domain was intended to harvest cryptocurrency wallet seeds or private keys. Defenders should continue to block the domain at network perimeter, enforce DNS sinkholing for the IP address 104.21.20.87, and monitor for any future re‑registration or similar domains using the Telcoin brand. Incident response teams should also flag any attempts to resolve or contact this domain as potentially malicious and consider adding the domain to internal blocklists.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/telcoincommunityStored page referenceIoC extraction recorded 2026-08-01 04:24:39 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 の評判はこのドメインに起因しません。
georgia.ns.cloudflare.comLocation describes the IP network.
8671cb6e9de748d20bc6e3cad241cc29feb532144854625c7146327c885065e5Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
vote-telcoin.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
https://radar.cloudflare.com/scan/9f71780f-aa94-4e8d-aa7d-92fa9cf8d560
11/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcevote-telcoin.network
View sourceコミュニティの 1 人が報告・初回確認 2026年3月5日
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 ↗
vote-telcoin.network)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.