VirusTotal
5 / 92 engine detections
보고서 열기“Captcha”
slon2.co — 확인되지 않음. 사기 유형: Impersonation. 증거 요약: VirusTotal 5/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); PhishDestroy score 88/100. 등록기관: PDR.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
5 / 92 engine detections
보고서 열기3 community references
보고서 열기Scan report
보고서 열기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
slon2.co is an impersonation phishing site that poses as a legitimate service to win visitors' trust and harvest what they enter. PhishDestroy first flagged it on 2026-10-03. As of 2026-10-19 the domain still responds, but its phishing content is no longer resolving through DNS. It is offline in practice, though the domain could be pointed at a live page again.
The page presents itself as a "Captcha" check, the familiar "prove you're human" step people click through without thinking. Impersonation sites use a gate like this to look routine before passing the visitor to a cloned login or wallet screen. Whatever is typed there, whether a password, a one-time code or a recovery phrase, goes to the operators, who then take over the account or empty the funds. The page title shows only a generic captcha, while our classification is brand impersonation based on how the site was used.
On 2026-10-14, five of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a low count, typical of young phishing domains that most scanners have not yet reached. Three AlienVault OTX threat pulses reference the domain, which shows other researchers have tracked it independently. Of the blocklists we monitor, only PhishDestroy currently lists it.
The domain was registered on 2026-08-02 through PDR Ltd. d/b/a PublicDomainRegistry.com, about two months before we detected it. That gap fits a domain bought ahead of time and left idle until a campaign was ready. Traffic runs through Cloudflare (AS13335) in the US, so the address visitors see belongs to the proxy, not the real origin server. The Google Trust Services certificate only gives the page a padlock, which says nothing about whether the site is trustworthy.
If you entered a password on slon2.co, change it right away on the real service and on any other account that shares it, then reset two-factor authentication and sign out other active sessions. If you typed a seed phrase, treat that wallet as compromised and move the funds to a new wallet. If you connected a wallet, review its token approvals and revoke anything you don't recognize. Security teams should block the domain at DNS and proxy level, search logs for visits since 2026-10-03, and report it to Cloudflare so the origin behind the proxy can be traced.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
lady.ns.cloudflare.comLocation describes the IP network.
7d639f2b98930e2d7de1de037d454b44b781dee26fdf28b585c9fed957908e29Saved 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 slon2.co · checked Oct 6, 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.
slon2.co
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
blocked→redirected
http_redirect
이용 불가→접속 가능
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
접속 가능→이용 불가
알 수 없음→live_content
content_served
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
No threat flag
View source5/92 engine detections
View source3 community references
View sourceslon2.co
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 ↗
slon2.co)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.