VirusTotal
1 / 92
إبلاغEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“编组 21”
Assessment based on the stored source evidence below. Review sources →
rainbitg.cc — آخر نشاط معروف (HTTP 200). انتحال العلامة التجارية: MetaMask. ملخص الأدلة: VirusTotal 1/92 (Forcepoint ThreatSeeker); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 78/100. مسجّل النطاق: Gname.
يبقى تحليل 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.
1 / 92
إبلاغEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 external matches
التفاصيلA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
إبلاغCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
التقرير المخزن
A preserved page image documents what the collector received; a capture is not a safety verdict.
اكتمل التحليل
إبلاغThis is the recorded automated analysis. Completion alone 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.
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.
The domain rainbitg.cc was listed on two external blocklists, MetaMask and SEAL, as of 2026-10-16, according to recorded evidence. Additionally, a PageSpeed performance score of 69 was documented for the domain on the same date.
On 2026-10-16, rainbitg.cc was included on both the MetaMask and SEAL blocklists. PhishDestroy also recorded an internal listing for the domain on this date. VirusTotal checked rainbitg.cc on 2026-10-15 and documented 1 detection out of 92 total scanners. The domain’s registration through Gname.com Pte. Ltd. was recorded on 2025-12-01.
The VirusTotal record contains a measurement of detections from a broad set of security scanners, providing insight into how rainbitg.cc was classified by various vendors. PhishDestroy documents an internal listing, while MetaMask and SEAL are external blocklist entries, each representing distinct forms of security intelligence. These dated records capture different aspects of the domain’s profile as observed by multiple sources.
For rainbitg.cc, it is important to preserve the VirusTotal and PhishDestroy records for future reference. The external blocklist entries from MetaMask and SEAL should also be stored to monitor any changes in their listings. Comparing these records at later dates will help track developments in the domain’s referenced security context.
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.
2 · external source matches
Gname.com Pte. Ltd. · 104.21.28.122 · DNS, TLS and retained responses
لا تُنسب سمعة Edge-IP إلى هذا المجال.
lia.ns.cloudflare.comLocation describes the IP network.
761f67c0db759f540eaa4f89bf52aa97660f584dc44fc101980c4937ef70bc24Saved 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 rainbitg.cc · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://rainbitg.cc/https://rainbitg.cc/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa4b97b2da99c180e-YYZkeep-alivegziptext/htmlFri, 16 Oct 2026 19:30:59 GMTMon, 02 Mar 2026 08:54:04 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=kOK1uqG8ZKjTUszNVm5pBmmu1%2BYSiA6BYXax2%2FCbdCLDaFtQf%2FvJf8ANwdRyGRsS5MD2Fteh4323BwoV%2BX4C1hWfyidhQGLioDscayW3wWM2q3JY1FbfPJ7LCsh22Q%3D%3D"}]cloudflarecfCacheStatus;desc="DYNAMIC"chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
A legacy response is stored, but it does not establish whether the file exists.
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
الملاحظات المخزنة المتعلقة بالمقارنة بين برامج الزحف والمتصفح لهذا المضيف، بالإضافة إلى فحص مباشر للبصمة الرقمية لأنظمة توزيع حركة المرور على غرار «كيتارو».
cloudflareLocal تم أرشفته في 2026-10-16 19:31:00 بالتوقيت العالمي المنسق (UTC)ملاحظة خاصة بالماسح الضوئي: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
لم تُحفظ نتيجة فحص مباشر بعد.
Collection history, report status and investigation channels
104.21.28.122.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
غير معروف
stale_current_evidence
غير معروف
9 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
Recovery steps, reporting contacts and complaint drafts
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 ↗
rainbitg.cc)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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. يتم عرض الطوابع الزمنية للمصدر حيثما كان ذلك متاحًا؛ يمكن أن تتغير أحكام التوفر والبائعين بعد التجميع.
عرض الموقع الذي تم التقاطه عنوان الصفحة “编组 21” وربما ينتحل شخصية MetaMask.
اعتبارًا من 2026-10-16 19:30:14 UTC، كان لدى rainbitg.cc اكتشافات من محركات الأمان 1.
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.
إذا كنت تعتقد أن هذه القائمة غير دقيقة، تقديم استئناف. للتعرف على منهجيتنا، قم بزيارة صفحة الأسئلة الشائعة.