VirusTotal
11 / 89 engine detections
보고서 열기“RobinCard | Robinhood Chain”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Telegram 사칭: robincard.wtf — 확인되지 않음. 증거 요약: VirusTotal 11/89 (ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet); URLQuery 4 alerts…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
11 / 89 engine detections
보고서 열기4 threat-system alerts
보고서 열기15/100
보고서 열기Threat flag recorded
보고서 열기DBL_PHISH
4 community references
보고서 열기provider verdict: clean
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
robincard.wtf is an impersonation phishing page that brands itself "RobinCard | Robinhood Chain". It borrows Robinhood's name and its blockchain project to pass as an official card or rewards offer. Its audience is Robinhood customers and crypto users following Robinhood Chain. PhishDestroy first flagged the domain on 2026-09-11. As of 2026-10-19 the domain still resolves, but its phishing content no longer loads.
The page title invents a "RobinCard" product tied to Robinhood Chain, which gives visitors a reason to sign up, claim or activate something. Pages built this way usually push the victim to enter Robinhood login details or to connect a crypto wallet and approve a transaction. Credentials let attackers take over the account. A signed wallet approval lets them move tokens out directly. Because the offer looks like an early-access launch tied to a new chain, victims tend to act fast instead of checking whether Robinhood announced it.
On 2026-09-20, 11 of 89 VirusTotal engines flagged the domain. They included ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing, Gridinsoft and Kaspersky. Google Safe Browsing classifies it as SOCIAL_ENGINEERING, and Spamhaus lists it in its DBL as a phishing domain. The wallet-focused blocklists of MetaMask and SEAL carry it alongside PhishDestroy, so many wallet users get a warning before the page loads. Four AlienVault OTX pulses reference it, which shows other researchers tracked the same campaign.
The domain was registered through NameCheap, Inc. on 2026-09-06, five days before PhishDestroy detected it. That short gap fits a site launched for a brief campaign. It is hosted on 76.76.21.21 in Amazon's AMAZON-02 network in the United States. It uses a free Let's Encrypt certificate, so the browser padlock only means the connection is encrypted. It says nothing about whether the site is genuine.
If you entered Robinhood credentials on this site, change your password immediately and reset two-factor authentication. Then review recent account activity and contact Robinhood support. If you connected a wallet or signed anything, revoke the token approvals granted from that address using a reputable approval-checking tool. Move the remaining funds to a new wallet if you approved unknown transactions or shared a seed phrase. Treat any "RobinCard" offer as fake unless Robinhood confirms it on its official channels. Defenders should block the domain and its IP at DNS and proxy level and search mail and chat logs for links to it.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x72BEBBe118Dc1cDb38a10db09C11DB53eC4C7977Format validated · Domain analysishttps://t.me/RobinCardCoinStored page referenceIoC extraction recorded 2026-09-13 04:00:15 UTC
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.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
dns1.registrar-servers.comdns2.registrar-servers.comeforward3.registrar-servers.compriority 10eforward1.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
014ccb7a6e7a5e3963aa472dfa1a4792f712e10be0a67deb706bcd68b0698524Saved 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 robincard.wtf · checked Sep 11, 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.
robincard.wtf
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
No flag recorded→Flag recorded
접속 가능
4 community references
View sourceThreat flag recorded
View source11/89 engine detections
View sourcePD-20260911-97E759
robincard.wtf
View sourcePage captured
View sourcePD-20260911-97E759 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
robincard.wtf)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.