Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 2 times, most recently ) to abuse@namecheap.com with VirusTotal detections, urlscan capture, legal violations, and full screenshot evidence.
More than 29 hours later, the phishing infrastructure remains reachable
.
Under ICANN RAA §3.18 accredited registrars are contractually obliged to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse.” Silence beyond 24 hours after a documented notification with verifiable evidence is not a timing issue — it is a policy decision to let the operation continue. PhishDestroy\'s position: where a registrar fails to act on clear evidence, the registrar has aligned itself with the operator of the scheme and bears co-responsibility for downstream harm caused to victims from the moment of notification onward.
Victim-assistance obligation. If NAMECHEAP INC doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 2 separate notifications over 29 hours, with the operation still active, the registrar took no measurable action to mitigate the harm caused by their client. The reasonable next step is direct help to any identified victims — contact & payment-trail disclosure, abuse-thread transcripts, registrant data preservation — since the registrar chose, by inaction, to extend the window of damage.
room-meet[.]xyz
“room-meet.xyz”
The threat classification supplied is generic phishing and the risk rating is high; the domain remains active as of the report date, July 27, 2026. Analysis of the available telemetry shows no publicly disclosed SSL certificate details, HTTP status codes, or page title information, so the content of the site has not been captured in the current intelligence set. The limited evidence therefore centers on infrastructure indicators: recent creation date, use of generic registrar‑provided name servers, and a single‑IP hosting model. The presence on multiple blocklists and the positive VirusTotal flag suggest that the domain is being used to host credential‑harvesting pages or other phishing payloads, consistent with the generic phishing label.
Defenders should add 192.64.119.253 to network‑level deny lists and enforce domain‑based filtering for room‑meet.xyz across perimeter and endpoint security solutions. Continuous monitoring of the authoritative name servers for changes, as well as periodic rescanning of the domain on VirusTotal and other sandbox services, is recommended to capture any evolution of the payload. Organizations that employ email or web gateway protections should ensure that the domain is blocked in URL filtering policies, and incident response teams should treat any traffic to the domain as potentially malicious, given the high risk rating and the existing blocklist entries.
Network Security Intelligence
Threat Response Pipeline
Public Blocklist Status
Evidence Capture
NAMECHEAP INCDomain Intelligence
(IS)
Technical detailsDNS, SSL SANs, timestamps
VirusTotal Analysis
Evidence & External Reports
ChainPatrol
Web-Check Were You Affected by This Site?
If you have interacted with this domain, entered personal information, or connected a cryptocurrency wallet — take immediate action. Below are resources to help you report the incident and protect yourself.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or generate an AI-powered complaint →
Related Domain Reports
More Domains at Namecheap 6 flagged
mm2free.com 
cryptofixeddeposite.com 
rpcresolvehub.org 
thecryptofixers.com 
rainbetcasinosuk.com About This Report: room-meet.xyz
This report presents the latest stored evidence available to PhishDestroy. Source timestamps are shown where available; availability and vendor verdicts can change after collection.
The site displays a page titled “room-meet.xyz”.
room-meet.xyz has been flagged by 1 security vendor as of July 28, 2026.
If you believe this listing is inaccurate, you can submit an appeal. For more information about our methodology, visit our FAQ page.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
Recommendations & Advice for Victims
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with room-meet.xyz — act now.
What should I do immediately?
Urgent
- Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
- Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
- 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
According to the FBI, the most important details are transaction data:
- Cryptocurrency addresses — scammer's wallet (e.g.,
0x5856...35985) - Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
- Transaction ID (hash) — the unique blockchain transaction identifier
- 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
room-meet.xyz) - 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)
- Chainabuse — flag scam wallets across exchanges & platforms
- Your crypto exchange — contact Coinbase/Binance/Kraken support to freeze scammer's address
- Local police — creates an official record, even if they can't act immediately
The FBI recovered over $1 billion in crypto fraud in 2024 thanks to victim reports. Your report matters.
How do crypto scams typically work?
- Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
- Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
- Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
- Recovery scams — victims targeted AGAIN by fake "recovery agents" demanding upfront fees. Always a scam
- Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
- AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
- Bookmark official sites — never click links from emails, DMs, or ads
- Read every approval — verify permissions before signing. Reject unlimited approvals
- Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
- "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
How big is the crypto scam problem?
- $51 billion flowed to illicit crypto wallets in 2024 — CoinLedger
- Pig butchering losses grew 40% year over year, now the fastest-growing fraud type
- Only ~5% of victims report — your report helps shut down criminal networks
- FBI recovered $1B+ in 2024 thanks to victim reports — FBI.gov
Sources: FBI · CoinLedger · WorldMetrics