VirusTotal
7 / 92 engine detections
Open report“Biofit | Biofit”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@rashost.com.
The latest stored availability evidence still shows the domain reachable; 4 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
7 / 92 engine detections
Open reportMalicious
Open reportScan report
Open report3 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
bfwell.shop is a fraudulent storefront whose page title reads simply "Biofit | Biofit". It is dressed up as a shop for the Biofit product, aimed at people searching online for that supplement. PhishDestroy first flagged it on 2026-10-16. As of 2026-10-19 it was still online and serving its shop content.
Fake shops like this copy the look of a real product page, often with discount banners, countdown timers and invented reviews, to push visitors into a quick purchase. The buyer enters card details, a shipping address and contact information at checkout. Typically nothing arrives, or a worthless substitute is shipped so the seller can contest a refund. The victim loses the purchase price and hands over payment and personal details that can be reused for further fraud.
urlscan.io rated the site malicious and specifically tagged it as a fake shop, which directly matches our classification. On VirusTotal, 4 of 92 engines flagged it on 2026-10-16: CRDF, G-Data, Gridinsoft and Netcraft. That count is low, so most security tools still let the site through. The domain also appears in 3 AlienVault OTX threat pulses, showing that other researchers have tracked it.
The domain was registered through Dynadot Inc. on 2026-06-10, about four months before we detected it. That gap suggests a domain set up in advance and then put into use as a shop. It is hosted on the Malakmadze Web LLC network in the United States. Its Let's Encrypt certificate gives it a browser padlock, which only means the connection is encrypted and says nothing about whether the seller is honest.
Do not order from bfwell.shop. If you already paid, contact your card issuer or payment provider right away, report the charge as fraud, request a chargeback and ask whether the card should be replaced. Keep any order confirmation emails as evidence. Watch for unexpected charges and for follow-up messages that use your name or address. Defenders should block the domain at DNS and web proxies and add it to mail and ad filtering, since detection by mainstream engines is still sparse.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
derek.ns.cloudflare.comvida.ns.cloudflare.comLocation describes the IP network.
466d824974777d5958cc3bdecf77e20f9a28952bc3ad2bedec3be56a38f0aa27Saved 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 bfwell.shop · checked Oct 16, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unavailable→Reachable
Reachable→Unavailable
Unknown→live_content
content_served
Unavailable→Reachable
Reachable→Unavailable
Unknown→live_content
content_served
Unknown→live_content
content_served
Unavailable→Reachable
Reachable→Unavailable
Unknown→live_content
content_served
Reachable
7/92 engine detections
View sourceNo threat flag
View source3 community references
View sourcePD-20261016-624351
bfwell.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bfwell.shop
PD-20261016-624351 Recipient: abuse@rashost.com If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
bfwell.shop)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.