VirusTotal
2 / 92 engine detections
Open report“Hair Growth Products | Hair Loss Solutions | Bask and Lather Co”
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; 2 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.
2 / 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
blco.shop presents itself as an e-commerce store for hair growth and loss solutions under the Bask and Lather Co brand. PhishDestroy first saw this site on 2026-10-17 and lists it as an active fake shop as of 2026-10-19.
The site mimics a legitimate hair-care retailer to lure visitors into purchasing products that are never shipped. Victims lose money and personal data after checkout. The page title and product branding suggest Bask and Lather Co, but the domain is unrelated to that company.
VirusTotal detected the site with 2 engines flagging it out of 92 checked on 2026-10-19, including alphaMountain.ai and Gridinsoft. urlscan.io’s verdict is malicious and it flagged the page as a fake shop. The domain is also listed on PhishDestroy’s blocklist.
The domain was registered on 2026-05-13 via Dynadot Inc. and resolves to 188.244.119.61 hosted by Malakmadze Web LLC in the US. TLS certificates are issued by Let’s Encrypt under YE2.
Anyone who visited or entered payment details should cancel their card and request a refund from their bank. Report the site to your payment provider and local consumer protection agency. Defenders should block the domain and IP and share the indicators with threat-intel feeds.
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.
amos.ns.cloudflare.commillie.ns.cloudflare.comLocation describes the IP network.
9b7dbe8c68d4ecb4c16becdb0ed8928afda813373853773e825a9b13c7907d32Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
img.blco.shopDomain recordm.blco.shopDomain recordwww.blco.shopDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of blco.shop · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://blco.shop/Cache-Control: private, no-cache, no-store, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8414a24acbb296164dc69289521a6be9baecdb44da319fd9f58a869ccd9322046summary_large_imageprivate, no-cache, no-store, max-age=0, must-revalidategziptext/html; charset=utf-8Sat, 17 Oct 2026 16:30:42 GMT; rel=preload; as="style"chunkedRSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch, Accept-Encoding1.1 CaddyValues retained by the collector; long values may be shortened during collection.
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
3 community references
View sourceNo threat flag
View source2/92 engine detections
View sourcePD-20261017-661588
Page captured
View sourceblco.shop
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
blco.shop
PD-20261017-661588 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 ↗
blco.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.