VirusTotal
6 / 91
“Problem loading page”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 12 days 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.
bitnest.life — لم يتم التحقق منها. انتحال العلامة التجارية: Binance; نوع الاحتيال: Impersonation. ملخص الأدلة: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, URLQuery); PhishDestroy score 88/100. مسجّل النطاق: PDR.
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
bitnest.life returned HTTP status 502 during an HTTP check performed on 2026-10-01, which provides a dated technical response for the domain. The domain was first observed in records on 2026-09-29, offering a reference point for subsequent monitoring.
The PhishDestroy internal listing includes bitnest.life as of the latest check. On 2026-10-01, OTX reported 4 pulses related to this domain. VirusTotal, checked on 2026-09-30, recorded 3 detections out of 91 scanners. The domain's registration date is 2025-12-02, and a PageSpeed check on 2026-09-29 returned a performance score of 67.
The PhishDestroy listing, OTX pulse count, and VirusTotal detections were each recorded on different dates, so their values reflect separate points in time. Because the HTTP status, PageSpeed score, and SSL scan also come from distinct dates, these sources provide independent technical snapshots rather than a single synchronized view. Comparing these dated records allows for tracking changes or trends, but does not indicate the domain's current state or content.
When reviewing bitnest.life, retain all dated evidence from each source to maintain a clear baseline for future comparison. Any new observations should be logged with their own dates and source names to support accurate tracking over time. During ongoing review, avoid submitting sensitive information to bitnest.life until further technical checks clarify its present behavior.
الملاحظات المخزنة المتعلقة بالمقارنة بين برامج الزحف والمتصفح لهذا المضيف، بالإضافة إلى فحص مباشر للبصمة الرقمية لأنظمة توزيع حركة المرور على غرار «كيتارو».
ملاحظة خاصة بالماسح الضوئي: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bitnest.life', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
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.vdsina.comns2.vdsina.comns3.vdsina.comns4.vdsina.commx.bitnest.lifepriority 10Location describes the IP network.
e292771094a9c1770dec3bbdce254b3660342f0bcdec979f64bf64243d0f6009Saved 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 bitnest.life · checked Sep 29, 2026
144.124.248.3. 16 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.
١٨٧ نطاقًا متشابهًا محفوظًا
عرض 100 من 187
PD-20260929-2E971D Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
Template-based draft · optional AI wording assistance requires separate consent
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب