VirusTotal
11 / 89 engine detections
Відкрити звіт“The 95% Project — Reclaim what fraud took from you”
фішинг: reclaimwise.finance — Останній відомий активний (HTTP 200). Зведення доказів: VirusTotal 11/89 (alphaMountain.ai, BitDefender, Chong Lua Dao…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
11 / 89 engine detections
Відкрити звіт17 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
reclaimwise.finance is an active crypto‑drainer site observed since its registration on 24 May 2026. The domain resolves to 185.158.133.1, a server located in Frankfurt, Germany, and serves content over HTTPS using a Google Trust Services/WE1 certificate. DNS is delegated to four name servers (ns3fqs.name.com, ns1hwy.name.com, ns2fln.name.com, ns4jnz.name.com) registered through Name.com, Inc. HTTP requests return status 200 and the page title “The 95% Project — Reclaim what fraud took from you”. The site is listed on three security blocklists and is actively blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal analysis shows a single detection out of 91 scanners, and Gridinsoft assigns a trust score of 0 / 100, reinforcing the malicious assessment. Infrastructure indicators, including the German IP address and recent domain age, are consistent with fast‑flux or short‑lived abuse campaigns targeting cryptocurrency users. No additional technical artifacts such as malware hashes or C2 endpoints have been published, so the exact draining mechanism remains unknown. Defenders should add reclaimwise.finance to deny‑list rules, monitor outbound connections to 185.158.133.1, and consider sinkholing the IP range. Continuous telemetry collection is advised to capture any evolving payloads or command‑and‑control activity associated with this crypto‑drainer operation.
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.
Репутація Edge-IP не пов’язана з цим доменом.
ns4jnz.name.comLocation describes the IP network.
74e965dffa2cf58c835cecc70d039e7d48c41238cc8317cb88f5f0ea36e98ff0Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
reclaimwise.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
No threat flag
View source17 community references
View source11/89 engine detections
View sourcereclaimwise.finance
View sourceПовідомив 1 учасник спільноти; уперше помічено 24.05.2026
Listed 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 ↗
reclaimwise.finance)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.