VirusTotal
13 / 91 engine detections
Відкрити звіт“Suspected phishing site | Cloudflare”
фішинг: nexusmutual.network — Контент недоступний. Зведення доказів: VirusTotal 13/91 (ADMINUSLabs, ChainPatrol, alphaMountain.ai, BitDefender, CRDF); URLScan…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
13 / 91 engine detections
Відкрити звітSuspicious
Відкрити звітШкідливий
Відкрити звітchecked — no match recorded
no community references
Відкрити звіт14 перевірено — блокувань немає
No threat flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain nexusmutual.network was created on March 12, 2026 and registered through HOSTINGER operations, UAB. It is currently resolved to the Cloudflare edge address 172.67.173.99, which belongs to AS13335 (Cloudflare, Inc.) and is geolocated in the United States. The authoritative nameservers are dorthy.ns.cloudflare.com and chase.ns.cloudflare.com, indicating that the site is fully protected by Cloudflare's CDN and utilizes HTTP/3. The TLS certificate presented is issued by Let’s Encrypt (E7), a standard free certificate authority, and the page title returned by the server is "Suspected phishing site | Cloudflare," consistent with Cloudflare's default block page for malicious content.
Gridinsoft assigns a trust score of 0 out of 100, reflecting a complete lack of confidence in the domain. Independent threat intelligence lists have catalogued the domain on three blocklists, specifically PhishDestroy, MetaMask, and SEAL, and VirusTotal records show that three of ninety-four scanned security vendors flagged the domain as malicious. The risk level is classified as elevated, and the current operational status is offline, suggesting that the hosting service has taken the site down or the operators have ceased activity.
While the available data confirms the domain’s involvement in a generic phishing campaign, the precise content and targeted brand, if any, remain unverified because no payload or landing page analysis is available. Defenders should continue to block the domain at the network perimeter, add it to internal deny lists, and monitor for any future re‑registration or reuse of the associated IP range. Ongoing DNS monitoring and TLS inspection are advised to detect any attempts to resurrect the site under a new certificate or hosting configuration.
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 не пов’язана з цим доменом.
chase.ns.cloudflare.comLocation describes the IP network.
c34540d2ed1e8751f7618081d79f21a2ea3bf71fa23ec963cab3223e09b5ec80Saved 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 nexusmutual.network · checked Mar 12, 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='nexusmutual.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
nexusmutual.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
0→1
13/91 engine detections
View sourceNo threat flag
View sourcenexusmutual.network
View sourceПовідомив 1 учасник спільноти; уперше помічено 12.03.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 ↗
nexusmutual.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.