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.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年4月23日score 15/1003 brand signals
IoC Extractionscanned 2026年8月1日0 wallet · 1 Telegram IoC
Submitted URLhttps://vote-telcoin.network/
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-15 22:18:15 UTCcurrent episode first observed: 2026-10-01 01:49:39 UTCobserved RIP window: 2026-09-15 22:18:15 UTC → 2026-10-01 01:49:39 UTC · 363.52hmidpoint estimate ≈ 2026-09-23 12:03:57 UTC · precision low · basis bounded
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.
技术 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
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.
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(IN)
