PhishDestroy first recorded fuzzy-bay.com on 2026-10-27. Stored VirusTotal result: 19/92 engines flagged. Malicious: 16. Suspicious: 3. Analysis time (as stored): 2026-10-27 19:14 UTC. Retrieved (as stored): 2026-10-27 20:27 UTC.
Page title: “fuzzy-bay.com | 523: Origin is unreachable”
More about the sources
Recorded security signals
Stored VirusTotal result: 19/92 engines flagged. Malicious: 16. Suspicious: 3. Analysis time (as stored): 2026-10-27 19:14 UTC. Retrieved (as stored): 2026-10-27 20:27 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded fuzzy-bay.com on 2026-10-27. Stored VirusTotal result: 19/92 engines flagged. Malicious: 16. Suspicious: 3. Analysis time (as stored): 2026-10-27 19:14 UTC. Retrieved (as stored): 2026-10-27 20:27 UTC. Risk: critical (evidence score 100/100). Registrar: Porkbun. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.
PhishDestroy added fuzzy-bay.com to its internal blocklist on 2026-10-27 after an intake flagged the domain due to multiple VirusTotal detections. The recorded page title was not available. An HTTP fetch on 2026-10-27 returned a 403 status, while a Cloudflare Radar scan on the same day reported a 200 response and a malware verdict.
How the scam works
The detections suggest the site may be used for malicious purposes, a pattern commonly seen with phishing, malware distribution, or fraudulent services, but no specific phishing page, credential‑stealing form, or malware payload was captured during the scans.
Evidence
VirusTotal (analysis on 2026-10-27) reported 16 malicious and 3 suspicious detections out of 92 engines (19 total). Google Safe Browsing (checked 2026-10-27) did not flag the domain. urlscan.io (capture 2026-05-21) gave an overall clean verdict but its engine analysis marked the site malicious with a score of 90. OTX listed three pulses referencing fuzzy-bay.com as of 2026-10-27, and PhishDestroy’s internal blocklist marks the domain as malicious while external blocklists showed no hits.
Infrastructure
The domain was registered on 2025-12-26 through Porkbun LLC and was 146 days old at the time of the latest check. Nameservers recorded were langston.ns.cloudflare.com and melody.ns.cloudflare.com. DNS records observed on 2026-10-27 listed Cloudflare IPv4 addresses 172.67.154.93 and 104.21.72.188, IPv6 addresses 2606:4700:3037::ac43:9a5d and 2606:4700:3036::6815:48bc, and the TLS certificate issued by Google Trust Services was valid until 2026-11-27.
What to do
Do not enter any credentials, personal information, or cryptocurrency keys on fuzzy-bay.com; if you have already done so, change the affected passwords and monitor accounts for unusual activity. Security teams should block the exact domain at the firewall, review logs for connections to the recorded IPs and DNS entries, and continue monitoring threat feeds for any new indicators related to this domain.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Urlscan result at: 2026-10-28 05:30:31; Urlscan enriched at: 2026-10-28 10:16:07
Technical metadata
PhishDestroy narrative
Narrative generation metadata
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
fuzzy-bay.com — Suspicious Domain
AI description
PhishDestroy flagged fuzzy-bay.com as suspicious on 2026-10-27 after VirusTotal detections and Cloudflare Radar labeling, though no malicious page was captured.
AI summary
Overview PhishDestroy added fuzzy-bay.com to its internal blocklist on 2026-10-27 after an intake flagged the domain due to multiple VirusTotal detections. The recorded page title was not available. An HTTP fetch on 2026-10-27 returned a 403 status, while a Cloudflare Radar scan on the same day reported a 200 response and a malware verdict. How the scam works The detections suggest the site may be used for malicious purposes, a pattern commonly seen with phishing, malware distribution, or fraudulent services, but no specific phishing page, credential‑stealing form, or malware payload was captured during the scans. Evidence VirusTotal (analysis on 2026-10-27) reported 16 malicious and 3 suspicious detections out of 92 engines (19 total). Google Safe Browsing (checked 2026-10-27) did not flag the domain. urlscan.io (capture 2026-05-21) gave an overall clean verdict but its engine analysis marked the site malicious with a score of 90. OTX listed three pulses referencing fuzzy-bay.com as of 2026-10-27, and PhishDestroy’s internal blocklist marks the domain as malicious while external blocklists showed no hits. Infrastructure The domain was registered on 2025-12-26 through Porkbun LLC and was 146 days old at the time of the latest check. Nameservers recorded were langston.ns.cloudflare.com and melody.ns.cloudflare.com. DNS records observed on 2026-10-27 listed Cloudflare IPv4 addresses 172.67.154.93 and 104.21.72.188, IPv6 addresses 2606:4700:3037::ac43:9a5d and 2606:4700:3036::6815:48bc, and the TLS certificate issued by Google Trust Services was valid until 2026-11-27. What to do Do not enter any credentials, personal information, or cryptocurrency keys on fuzzy-bay.com; if you have already done so, change the affected passwords and monitor accounts for unusual activity. Security teams should block the exact domain at the firewall, review logs for connections to the recorded IPs and DNS entries, and continue monitoring threat feeds for any new indicators related to this domain. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/019e49b7-c100-7767-b98a-3dd6c18a75e0/ Cloudflare Radar report: https://radar.cloudflare.com/scan/d6cae964-3a26-401b-9d3a-f4b933a1ab7d Stored capture screenshot: https://urlscan.io/screenshots/019e49b7-c100-7767-b98a-3dd6c18a75e0.png Cloudflare Radar screenshot (2026-10-27T19:58:28Z): https://screenshots.phishdestroy.io/cf/d6cae964-3a26-401b-9d3a-f4b933a1ab7d.png URLScan screenshot (2026-05-20T14:00:34Z): https://screenshots.phishdestroy.io/us/019e45b0-147b-7438-a63b-8f1e4af8d18c.png URLScan capture report: https://urlscan.io/result/019e45b0-147b-7438-a63b-8f1e4af8d18c/ URLScan screenshot (2026-10-27T19:46:14Z): https://screenshots.phishdestroy.io/us/01a17ee6-05ca-7171-8ad8-3e6a942051f0.png URLScan capture report: https://urlscan.io/result/01a17ee6-05ca-7171-8ad8-3e6a942051f0/ URLScan screenshot (2026-10-27T20:02:55Z): https://screenshots.phishdestroy.io/us/01a17ef5-57d8-7539-b3f2-656c84c87b1e.png URLScan capture report: https://urlscan.io/result/01a17ef5-57d8-7539-b3f2-656c84c87b1e/ VirusTotal report: https://www.virustotal.com/gui/domain/fuzzy-bay.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=fuzzy-bay.com Archived copy: https://web.archive.org/web/20261027194508/https://fuzzy-bay.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
PhishDestroy rates fuzzy-bay.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-27. Stored VirusTotal result: 19/92 engines flagged. Malicious: 16. Suspicious: 3. Analysis time (as stored): 2026-10-27 19:14 UTC. Retrieved (as stored): 2026-10-27 20:27 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is fuzzy-bay.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on fuzzy-bay.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used fuzzy-bay.com?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Issued by Google Trust Services / WE1· stored validity ends in 5 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.154.93
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
langston.ns.cloudflare.com
melody.ns.cloudflare.com
SOA
nsname: langston.ns.cloudflare.com
hostmaster: dns.cloudflare.com
serial: 2415428532
refresh: 10000
retry: 2400
expire: 604800
minttl: 1800
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-08-29 22:03:39
Valid until
2026-11-27 23:02:15
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0680d59118d9798ec9653777e820853e87110348f99476f5a3183e3f5575f496Certificate names · 2 SANs
fuzzy-bay.com
*.fuzzy-bay.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Resolved
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-22 11:16 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:16 UTClast content: 2026-11-22 11:16 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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:54 UTC.
Recorded events: 15. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
6 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+305 d 17 h
Added to PhishDestroy+28 min
AlienVault OTX
3 community references
+29 min
Cloudflare Radar
Phishing
+13 min
Wayback Machine
Page archived
+1 min
Added to PhishDestroy
fuzzy-bay.com
+28 min
VirusTotal
19/92 engine detections
+159 d 10 h
URLScan
Malicious · engine verdict · score 90
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
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 fuzzy-bay.com)
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)
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
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 →
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.