VirusTotal
18 / 91 engine detections
Відкрити звіт“Page 1”
фішинг: xrp-flaress.network — Контент недоступний. Зведення доказів: VirusTotal 18/91 (ADMINUSLabs, ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
18 / 91 engine detections
Відкрити звіт1 threat-system alert
Відкрити звіт4/13
Шкідливий
Відкрити звітno community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | xrp-flaress.network |
malicious | Sinkholed |
PhishDestroy threat report
This domain, xrp-flaress.network, is associated with a crypto drainer phishing threat, which poses a high risk to users. Such websites are designed to trick individuals into revealing their cryptocurrency wallet credentials or private keys, leading to potential financial loss and compromise of personal information. The threat is categorized as generic phishing, but the specific focus on crypto drainers highlights the targeted nature of the attack.
Analysis indicates that xrp-flaress.network has been flagged by 18 out of 95 security vendors on VirusTotal, suggesting a significant level of suspicion and potential malicious activity. The domain was created on May 26, 2026, and is registered through Dynadot Inc, a domain registrar. Additionally, the site uses technologies such as Tailwind CSS, LiteSpeed, and HTTP/3, which are common in modern web infrastructures but do not inherently indicate malicious intent. The domain's current status is offline, and it appears on four security blocklists, further corroborating the high risk level.
If a user visited xrp-flaress.network, it is crucial to take immediate action to secure any cryptocurrency wallets and personal information. Users should change their wallet passwords and enable two-factor authentication if available. It is also recommended to monitor wallet transactions and credit reports for any unauthorized activity. Reporting the incident to relevant cybersecurity authorities and informing one's cryptocurrency exchange platform can help mitigate potential damage and prevent further incidents.
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.
ns1.globaldnsnetwork.comns2.globaldnsnetwork.comxrp-flaress.networkpriority 0Location describes the IP network.
a023c0687ddb267da808782267c4607ee4b6627a6cea43e0c3fb226fe5cc9fe8Saved 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 xrp-flaress.network · checked Jun 26, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='xrp-flaress.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
xrp-flaress.network
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
5→18
18/91 engine detections
View sourceNo threat flag
View sourcePage captured
View sourcexrp-flaress.network
View sourcePD-20260531-EB4159
Повідомив 1 учасник спільноти; уперше помічено 31.05.2026
PD-20260531-EB4159 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains 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 ↗
xrp-flaress.network)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.