VirusTotal
13 / 92 engine detections
Відкрити звіт“Solana”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ownregistrar.com.
The latest stored availability evidence still shows the domain reachable; 6 days 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.
підробка під Solana: einsols.com — Неперевірений. Зведення доказів: VirusTotal 13/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft); URLQuery 2 det.; 2…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
13 / 92 engine detections
Відкрити звіт2 det.
Відкрити звітШкідливий
Відкрити звіт4 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
einsols.com is an impersonation phishing page that poses as Solana. The page is simply titled "Solana", and the domain itself hides "sol" inside a meaningless word. It targets holders of SOL and Solana-based tokens. PhishDestroy first flagged it on 2026-10-13. When last checked on 2026-10-19, the domain was still up but no longer serving its phishing content.
Pages like this copy Solana's branding so that a visitor arriving from a search ad, social post or direct message believes they are on an official site. The visitor is then pushed toward a wallet action. That might be connecting a wallet to claim a reward or fix an alleged problem, approving a transaction that quietly transfers assets, or typing a recovery phrase into a form. Any of these hands control of the wallet's SOL and tokens to the operators. Solana transfers settle within seconds and cannot be reversed.
On 2026-10-17, 13 of 92 VirusTotal engines classified the domain as malicious. They include BitDefender, ESET, Kaspersky, Fortinet, G-Data, Emsisoft, CRDF and alphaMountain.ai. Several of these vendors protect consumer browsers and endpoints directly. The domain is also blocked by MetaMask and SEAL, both focused on crypto threats, in addition to PhishDestroy. It appears in 4 AlienVault OTX threat pulses, which shows other researchers tracked it independently.
The domain was registered on 2026-10-10 through OwnRegistrar, Inc. and was flagged three days later. A fresh domain used almost immediately is typical of short-lived phishing campaigns. It sits behind Cloudflare (AS13335, United States) at 172.67.163.46, which conceals the actual origin server. Its Let's Encrypt certificate gives the page a browser padlock, and that padlock says nothing about whether the site is legitimate.
If you connected a wallet to einsols.com, open the wallet's connected-sites list and remove the site. Then review recent activity and revoke any token approvals or delegations you do not recognise. If you entered a seed phrase or private key, treat that wallet as compromised. Create a new wallet and move any remaining assets to it right away, because revoking approvals will not help in that case. Only reach Solana and your wallet provider through bookmarks or official app stores. Defenders should block the domain at DNS and proxy level and check logs for users who visited it after 2026-10-10.
Last checked
Репутація Edge-IP не пов’язана з цим доменом.
patrick.ns.cloudflare.comsuzanne.ns.cloudflare.comLocation describes the IP network.
b5a1f947b70eb804d77d46c4717274ff6210f29bcc1bd28a48ddb2415e31029aSaved 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 einsols.com · checked Oct 13, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://einsols.com/https://einsols.com/Content-Type: text/html; charset=utf-8Server: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa49f8ef5694bc486-EWRkeep-alivegziptext/html; charset=utf-8Tue, 13 Oct 2026 16:00:39 GMTTue, 13 Oct 2026 16:00:07 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=N4uFQZ%2FgN173RnXGM5cydo6lwasU42GM%2FqxdNGdYlboDstBZDrTkndJpgKlWDVFKgpgQGSqfQwf%2B58EekE8INuDrCgmTuySmJ%2FOBirbTn78YkFuIUkv7HCIazd%2B0Ug%3D%3D"cloudflarecfCacheStatus;desc="DYNAMIC"chunkedaccept-encodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
live_content→dns_inactive
dns_nxdomain
Невідомо→live_content
content_served
Доступний
No threat flag
View source13/92 engine detections
View source4 community references
View sourcePD-20261013-BE15D1
einsols.com
View sourcePage captured
View sourceЗбережено 118 схожих доменів
Показано 100 із 118
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
einsols.com
PD-20261013-BE15D1 Recipient: abuse@ownregistrar.com Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
einsols.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
Аналіз загроз за допомогою збереженого списку блокувань, 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.