VirusTotal
4 / 92 engine detections
Open report“Soft, silky skin starts with Bleame! | Soft, silky skin starts with Bleame!”
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; 44 hours 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.
4 / 92 engine detections
Open reportMalicious
Open reportScan report
Open report4 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.
AI-assisted evidence review
bleamecare.shop presents itself as a legitimate online store selling skin‑care products, using the page title “Soft, silky skin starts with Bleame!”. The site mimics a typical e‑commerce checkout to lure consumers interested in beauty and personal‑care items. PhishDestroy first saw the domain on 2026-10-17. The site remains alive and serving content as of 2026-10-19.
Visitors are greeted by a promotional banner and product listings that suggest a real retailer, then prompted to add items to a cart and provide credit‑card, billing and shipping information. The checkout form forwards the entered payment details to the operators, who can charge the cards, commit identity theft, or sell the data on underground markets. No genuine order is fulfilled, leaving the victim without the advertised product.
VirusTotal flagged bleamecare.shop as malicious in 4 of 92 scanning engines, with detections from alphaMountain.ai, Gridinsoft, SOCRadar and Webroot. urlscan.io returned a malicious verdict and specifically marked the site as a fake shop. PhishDestroy added the domain to its blocklist and the domain appears in four OTX pulses.
The domain was registered on 2026-03-21 through Spaceship, Inc. It is hosted on IP 188.244.119.61, part of the malakmadze Malakmadze Web LLC network located in the United States. TLS certificates are issued by Let’s Encrypt / YE2.
Anyone who entered personal or payment information on bleamecare.shop should immediately contact their bank or card issuer to dispute any unauthorized charges. Change passwords for any accounts that may share credentials and monitor credit reports for suspicious activity. Report the incident to local consumer‑protection agencies and file a phishing report with major email providers. Security teams should block the domain at DNS and proxy layers, add it to internal threat‑intel feeds, and share the indicator with industry ISACs.
urlscan.io scan and screenshot: https://urlscan.io/result/01a14af7-ff2f-74aa-b6a6-0faea6568385/
VirusTotal report: https://www.virustotal.com/gui/domain/bleamecare.shop
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=bleamecare.shop
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
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.
fb3788b0d3e586d1c4c6a20527c911b1801e9c79ca5600afcd3d9e2e34f0c63eSaved 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.bleamecare.shopDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of bleamecare.shop · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bleamecare.shop/Cache-Control: private, no-cache, no-store, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-89ae80c2e9233f4f0e68784459bf637c1bfb4b2a25f437b44cfae9c8e3bb3fc98summary_large_imageprivate, no-cache, no-store, max-age=0, must-revalidategziptext/html; charset=utf-8Sat, 17 Oct 2026 17:39:19 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.
Unknown→live_content
content_served
Unavailable→Reachable
Reachable→Unavailable
3→4
Unknown→live_content
content_served
Reachable
4 community references
View sourceNo threat flag
View source4/92 engine detections
View sourcePD-20261017-56C053
Page captured
View sourcebleamecare.shop
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bleamecare.shop
PD-20261017-56C053 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 ↗
bleamecare.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.