VirusTotal
13 / 89
إبلاغEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“FATAL EXCEPTION 0xE2”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse-trusted.savcom@in.wixanswers.com.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
modanix.digital — آخر نشاط معروف (HTTP 200). انتحال العلامة التجارية: Genericemail; نوع الاحتيال: Impersonation. ملخص الأدلة: VirusTotal 13/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET); URLQuery 2 alerts; URLScan malicious verdict; Spamhaus DBL_SPAM; CF Radar malicious; PhishDestroy score 100/100. مسجّل النطاق: Sav.com.
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
13 / 89
إبلاغEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 threat-system alerts
إبلاغAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
malicious
إبلاغThis is the recorded automated analysis. Completion alone is not a safety verdict.
DBL_SPAM
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
إبلاغCommunity publication references, not a vendor verdict or evidence of a common operator.
التقرير المخزن
View stored capture ↗ إبلاغA preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
إبلاغA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
التفاصيلA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | modanix.digital |
malicious | Sinkholed |
| DNS4EU | modanix.digital |
malicious | Sinkholed |
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
Stored evidence for modanix.digital: VirusTotal recorded 2 detections among 90 scanners on 2026-09-03. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for modanix.digital. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 2 detections among 90 scanners in the stored snapshot dated 2026-09-03. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-03 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
OpenPhish are recorded as named external blocklist observations for modanix.digital in the snapshot dated 2026-09-03. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains modanix.digital as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed modanix.digital on 2026-09-03. The OpenPhish blocklist snapshot is dated 2026-09-03 and remains a separate event in the stored timeline. The registration date is separately recorded as 2025-11-23. A URLScan reference was stored on 2026-09-03 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
The source stores 64.247.178.120 as the observed address in this record. The registration date for modanix.digital is recorded as 2025-11-23. The stored ASN observation records 31898 and Oracle Corporation in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The modanix.digital record states that VirusTotal recorded 2 detections among 90 scanners on 2026-09-03. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-03. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 64.247.178.120. The supported conclusion is bounded to the exact stored observations for modanix.digital. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to modanix.digital during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain modanix.digital as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to modanix.digital. The stored record does not justify extending that rule to 64.247.178.120 or to other infrastructure records.
21 · datasets with records / 10 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Sav.com, LLC · 64.247.178.120 · DNS, TLS and retained responses
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.
cris.ns.cloudflare.comrayne.ns.cloudflare.comLocation describes the IP network.
f346e607ada0a49d5ac13dc686ea9c5b5f0f4f42636f8657064de774c0a95b59Saved 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 modanix.digital · checked Sep 3, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
الملاحظات المخزنة المتعلقة بالمقارنة بين برامج الزحف والمتصفح لهذا المضيف، بالإضافة إلى فحص مباشر للبصمة الرقمية لأنظمة توزيع حركة المرور على غرار «كيتارو».
Caddyملاحظة خاصة بالماسح الضوئي: alive_content: raw=ok; http=200; via=http_proxy; server=Caddy
1 · outbound report records
64.247.178.120.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→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
live_content→غير معروف
stale_current_evidence
غير معروف→live_content
content_served
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
live_content→غير معروف
probe_inconclusive
غير معروف→live_content
content_served
غير معروف
probe_inconclusive
يمكن الوصول إليه
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
PD-20260903-EDF6C9 Recipient: abuse-trusted.savcom@in.wixanswers.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Recovery steps, reporting contacts and complaint drafts
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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 ↗
modanix.digital)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب
يقدم هذا التقرير أحدث الأدلة المخزنة المتاحة لـ PhishDestroy. يتم عرض الطوابع الزمنية للمصدر حيثما كان ذلك متاحًا؛ يمكن أن تتغير أحكام التوفر والبائعين بعد التجميع.
عرض الموقع الذي تم التقاطه عنوان الصفحة “FATAL EXCEPTION 0xE2” وربما ينتحل شخصية Genericemail.
اعتبارًا من 2026-09-13 02:11:02 UTC، كان لدى modanix.digital اكتشافات من محركات الأمان 13.
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
إذا كنت تعتقد أن هذه القائمة غير دقيقة، تقديم استئناف. للتعرف على منهجيتنا، قم بزيارة صفحة الأسئلة الشائعة.