Skip to security report
Analytics Dashboard
Domain security report
rainbitg.cc favicon

rainbitg.cc

“编组 21”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 1/92 Stored blocklist matches: 2 Automated brand label: MetaMask
Oct 16, 2026 MetaMask CDN
API
Registrar
Gname
Resolved IP
104.21.28.122
Registered
Dec 1, 2025
1 sources
The capture source is temporarily unavailable.
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 1. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
1 det.
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates
Google Trust Services / WE1 · Hostname coverage not recorded
Age
11 mo
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed

Source evidence

7 · sources

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.

VirusTotal

1 / 92

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

Observation time not recorded
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
1/92
URLScan
Stored capture

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.

Assessment

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.

Recorded Evidence

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.

Interpretation

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.

Recommended Actions

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.

Data coverage & collection

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.

Recorded dataPartial recordUTC
VirusTotal
1 / 92 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Gname.com Pte. Ltd.Collection time not recorded
Network & DNS
104.21.28.122 · 1 · nameserversCollection time not recorded
TLS certificate
Google Trust Services / WE1
Page captures
1 · retained captures
HTML archives
1 · retained responses
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
69/100 · mobile performance
Availability history
2 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Response records
  • Recorded subdomains
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Gname.com Pte. Ltd. · 104.21.28.122 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Gname SG(SG)
Abuse contact["complaint@gname.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for rainbitg.cc →
RegistrationCreated Dec 1, 2025 (319d) — Expires Dec 1, 2026
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 16, 2026
DOM Analysisanalyzed Oct 17, 2026score 78/100
Submitted URLhttp://rainbitg.cc/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.28.122
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1
  • lia.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-23 15:44:02
Valid until
2026-12-22 16:43:54
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 22:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint761f67c0db759f540eaa4f89bf52aa97660f584dc44fc101980c4937ef70bc24

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 104.21.28.122rapiddns.io

Latest Classified Outcome 2026-10-17 01:47:56 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-17 01:47:56 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 01:47:56 UTC last content: 2026-10-17 01:47:56 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
Forcepoint ThreatSeeker
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of rainbitg.cc · checked Oct 16, 2026

69
Needs Work
Performance
FCP
3.92s
First Contentful Paint
LCP
4.15s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
5ms
Total Blocking Time
SI
15.92s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://rainbitg.cc/
Final URL: https://rainbitg.cc/
Response
HTTP 200
HTML body
15.2 KB
Compressed
7.9 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4b97b2da99c180e-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Fri, 16 Oct 2026 19:30:59 GMT
Last-Modified
Mon, 02 Mar 2026 08:54:04 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=kOK1uqG8ZKjTUszNVm5pBmmu1%2BYSiA6BYXax2%2FCbdCLDaFtQf%2FvJf8ANwdRyGRsS5MD2Fteh4323BwoV%2BX4C1hWfyidhQGLioDscayW3wWM2q3JY1FbfPJ7LCsh22Q%3D%3D"}]
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-16 19:31:00 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-16 19:31:00 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-16 19:31:00 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
cloudflare
Capture routing
Local archived 2026-10-16 19:31:00 UTC

Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-10-16 19:30:06 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.28.122.
Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown

    stale_current_evidence

  3. Availability monitor · First collection record

    Unknown

Threat Response Pipeline

Discovery
Analysis
Monitoring

9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
rainbitg.cc detected and queued for full analysis
Oct 16, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
1/92 recorded on VirusTotal
Oct 16, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 17, 2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Oct 16, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Lookalike domains

79 stored lookalike domains

etamask.io omission Internal report meetamask.io repetition Internal report megamask.io replacement Internal report metam.ask.io subdomain Internal report metamaak.io replacement Internal report metamadk.io replacement Internal report metamaks.io transposition Internal report metamassk.io insertion Internal report metamsask.io insertion Internal report metamssk.io replacement Internal report metanask.io homoglyph Internal report metanmask.io homoglyph Internal report
Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 1 det. ChainPatrol URLQuery SSL Labs Hostname coverage not recorded CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including rainbitg.cc)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: rainbitg.cc

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “编组 21”. Apparent target: MetaMask.

VirusTotal detections for rainbitg.cc: 1 (2026-10-16 19:30:14 UTC).

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.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/rainbitg.cc"
  title="PhishDestroy threat report for rainbitg.cc"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>