VirusTotal
4 / 89 engine detections
Відкрити звіт“Not Acceptable!”
домен у блоклистах: phantext.pro — Контент недоступний. Зведення доказів: VirusTotal 4/89 (Forcepoint ThreatSeeker, Fortinet, URLQuery, Webroot); 2 external…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
4 / 89 engine detections
Відкрити звітchecked — no detections recorded
Відкрити звіт4 community references
Відкрити звітprovider verdict: clean
Відкрити звіт80/100
Відкрити звіт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
phantext.pro is an impersonation phishing site built to pass itself off as a legitimate crypto service. Its listing on the MetaMask and SEAL blocklists places its audience among cryptocurrency wallet users. PhishDestroy first detected it on 2026-09-17, only five days after registration. The site went offline on 2026-09-19, and on 2026-10-19 its DNS was still inactive.
Impersonation pages copy the look, wording and flow of a trusted wallet or crypto brand, then ask the visitor to log in, verify a wallet, import a recovery phrase or sign a transaction. Whatever is typed or signed goes straight to the operator. A seed phrase gives full control of the wallet, and a malicious signature can authorize transfers of tokens. When we last loaded the page, its title read "Not Acceptable!", a server error string, while the domain itself is classified as an impersonation phishing page.
VirusTotal returned 4 detections out of 89 engines on 2026-09-18. The flagging vendors were Forcepoint ThreatSeeker, Fortinet, URLQuery and Webroot. That count is low, but it is typical for a domain checked within days of going live, and the classification does not depend on it alone. MetaMask and SEAL, both focused on crypto threats, list the domain alongside PhishDestroy. It also appears in 4 AlienVault OTX threat pulses.
The domain was registered through Spaceship, Inc. on 2026-09-12 and was being flagged within a week. That short gap matches the pattern of throwaway phishing domains set up for a brief campaign. It resolved to 162.241.85.94 on the Unified Layer network in the United States, a large shared-hosting provider. The whole operation lasted about a week, from registration to going offline on 2026-09-19.
If you entered a recovery phrase or private key on phantext.pro, treat that wallet as compromised. Create a new wallet on a trusted device and move any remaining funds there immediately. If you connected a wallet or signed anything, review and revoke token approvals with a reputable approval-checker, and watch for unexpected outgoing transactions. If you entered a password, change it everywhere you reused it and turn on two-factor authentication. Defenders should block the domain and its hosting IP, search proxy and DNS logs for visits between 2026-09-12 and 2026-09-19, and warn users who may have connected wallets during that window.
Last checked
rns19.webhostbox.netrns20.webhostbox.netmail.phantext.propriority 0Location describes the IP network.
65f988ac0e21a2a1bc2601cd5239b689d9eccf657ad04f2fe847ef925e6e44aaSaved 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 phantext.pro · checked Sep 17, 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.
phantext.pro
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
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Доступний→Недоступно
0→4
Доступний
4 community references
View sourceNo threat flag
View source4/89 engine detections
View sourcePD-20260917-DE4B22
Page captured
View sourcephantext.pro
View sourcePD-20260917-DE4B22 Recipient: abuse@spaceship.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 ↗
phantext.pro)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.