VirusTotal
9 / 92 engine detections
보고서 열기“Offline”
326815-crypto.com — 확인되지 않음. 브랜드 사칭: Crypto.com; 사기 유형: Impersonation. 증거 요약: VirusTotal 9/92 (alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet); Google Safe Browsing flagged; Spamhaus DBL_SPAM; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. 등록기관: Dynadot.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
9 / 92 engine detections
보고서 열기Suspicious
보고서 열기Threat flag recorded
보고서 열기DBL_SPAM
2 community references
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
326815-crypto.com is an impersonation phishing domain that borrows the Crypto.com name and pads it with a numeric prefix so it looks like an official regional or campaign subdomain. It targets Crypto.com customers and crypto holders who might trust a familiar brand in the address bar. PhishDestroy first flagged it on 2026-10-08. As of 2026-10-19 the domain still resolves, but its page content does not load.
Lookalike exchange domains like this one copy the target brand's login or wallet screens. Victims who enter their email, password and one-time codes give attackers live access to their account. Some variants instead push visitors to connect a wallet or send a "verification" deposit, and the funds are gone the moment they leave. The page currently carries the title "Offline", which does not by itself show phishing content, while our classification rests on the domain's impersonation of Crypto.com and the detections below.
Nine of 92 VirusTotal engines flagged the domain on 2026-10-08. They include Google Safe Browsing, Kaspersky, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF and Gridinsoft, a spread of independent vendors rather than a single feed. Google Safe Browsing classifies it as SOCIAL_ENGINEERING, so Chrome and other browsers that use it should show a warning. MetaMask and SEAL list it alongside PhishDestroy, which places it on wallet-focused blocklists. Spamhaus DBL lists it as spam, and it appears in two AlienVault OTX threat pulses.
The domain was registered through Dynadot Inc on 2026-09-17, three weeks before it was detected, which fits the short build-and-launch cycle typical of throwaway phishing domains. It is hosted at 217.60.76.92 on the Netiface America, Inc. network, located in the Netherlands. Its Let's Encrypt certificate gives it a padlock in the browser, which shows the connection is encrypted but says nothing about who runs the site.
If you typed Crypto.com credentials into this site, change your password from the official app right away. Reset two-factor authentication, sign out all other sessions, and review withdrawal addresses and recent activity. If you connected a wallet here, revoke any token approvals granted during that session, and move funds to a fresh wallet if you entered a seed phrase. Never send a deposit or fee to "unlock" an account through a link like this. Defenders should block the domain and its IP at DNS and proxy level, and search mail and web logs for users who visited it after 2026-09-17.
urlscan.io scan and screenshot: https://urlscan.io/result/01a0b237-0898-759d-b9ff-51082fe0935b/
VirusTotal report: https://www.virustotal.com/gui/domain/326815-crypto.com
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=326815-crypto.com
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
Last checked
ns2.dyna-ns.netLocation describes the IP network.
aca82c528b567922c32a24e510993c4c4d47523fd4a47f422ea578cff557b376www.326815-crypto.comSaved 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.326815-crypto.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of 326815-crypto.com · checked Oct 8, 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.
326815-crypto.com
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
No flag recorded→Flag recorded
Threat flag recorded
View source2 community references
View source9/92 engine detections
View source326815-crypto.com
View sourceListed 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 ↗
326815-crypto.com)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.