Redacted domain dossier, minus the house style
We are far too editorially nervous to tell you whether the upstream publisher is correct. We can, however, preserve the dossier, keep the indicators readable, and route every external exit through the source gate.
Why this matters — ICANN RAA §3.18 obligation
On THE ENABLERS REGISTRY delivered an evidence-backed abuse report
to abuse@name.com with VirusTotal detections, urlscan capture, legal violations, and full screenshot evidence.
More than 4 months later, the possibly 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. THE ENABLERS REGISTRY\'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.
Technical analysis revealed the site was flagged by 21 out of 95 VirusTotal vendors, with detections from ADMINUSLabs, Criminal IP, alphaMountain.ai, BitDefender, and Chong Lua Dao. The domain was registered through [REDACTED], hosted on IP address 34.111.179.208 in the United States ([REDACTED]), and created on March 3, 2026. Nameservers were anderson.ns.IANA #1910.com and liz.ns.IANA #1910.com. No SSL certificate details were provided.
The site is currently offline, with a GridinSoft trust score of 0 out of 100 and a DOM risk score of 73, indicating a high-risk, malicious domain. Its active status was brief, and the site no longer poses an immediate threat, but the impersonation of Facebook and high detection rates confirm its malicious intent.
Network Security Intelligence
Threat Response Pipeline
Public Blocklist Status
Evidence Capture
Domain Intelligence
(US)
Kansas City, USTechnical detailsDNS, SSL SANs, timestamps
Shared-IP Neighbors · 41 other domains
Related Campaign Members · 8 sharing fingerprint
Technologies · 6 identified
JavaScript runtime built on Chrome V8 engine for server-side development.
Suite of cloud computing services running on Google infrastructure.
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Content delivery network built on Google global edge infrastructure.
Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.
VirusTotal Analysis
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of rblx.foo · checked Mar 16, 2026
Evidence & External Reports
URLScan
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
Other Domains on 34.111.179.208 6 possibly phishing domains
This IP hosts multiple possibly phishing domains — infrastructure shared across campaigns
More Domains at [REDACTED] 6 flagged
Other Facebook Impersonation Domains
These domains also target Facebook users. View all Facebook threats →
About This Report: rblx.foo
This report presents the latest stored evidence available to THE ENABLERS REGISTRY. Source timestamps are shown where available; availability and vendor verdicts can change after collection.
The site displays a page titled “Kyxn Dev — Developer Platforms & APIs”, which may be designed to impersonate Facebook.
rblx.foo has been flagged by 21 security vendors as of July 23, 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 Possibly phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent possibly 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 rblx.foo — 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 possibly 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
rblx.foo) - 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 NASDAQ:COIN/LEI:5493004F7TI6QBM4WX72/FinCEN MSB #31000023456789 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 [REDACTED]/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 possibly phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Use a hardware wallet ([REDACTED], [REDACTED]). 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 THE ENABLERS REGISTRY 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
Archive note
If the page below still says “we” or sounds suspiciously confident, that remains the upstream publisher speaking. TER only preserves the record, strips the house branding, and keeps exits wrapped through the source gate.