VirusTotal
2 / 92 engine detections
Open report“Cosmetics by Bloom | Bloom Cosmetics”
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 reportDBL_SPAM
Malicious
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.
PhishDestroy threat report
bloomcosmeticsbeauty.shop hosts an impersonation phishing page that pretends to be the official Bloom Cosmetics online store. It targets shoppers and potential customers of the Bloom Cosmetics brand. PhishDestroy first observed the site on 2026-10-17. The site remains live as of the last check on 2026-10-19.
The page presents a storefront titled “Cosmetics by Bloom | Bloom Cosmetics”, copying the look and language of the legitimate brand. Visitors are prompted to log in or provide payment details to purchase products that do not exist. Collected credentials can be reused to access real accounts or to conduct fraudulent transactions. The impersonation kit leverages a generic e‑commerce template to appear trustworthy.
VirusTotal scans flagged the domain in 2 of 92 engines, with alphaMountain.ai and Gridinsoft raising alerts. urlscan.io returned a malicious verdict and identified the site as a fake shop. PhishDestroy and Spamhaus list the domain on their blocklists, and the Open Threat Exchange records four active pulses referencing it. These independent detections corroborate the impersonation classification.
The domain was registered on 2026-05-25 through Dynadot Inc. Hosting is provided from IP 23.252.79.88, belonging to the Malakmadze Web LLC network in Georgia. The site uses a Let’s Encrypt / YE1 TLS certificate for HTTPS. All infrastructure details are consistent with typical low‑cost abuse setups.
Anyone who entered login credentials or payment information should change those passwords immediately, contact their financial institution, and monitor accounts for unauthorized activity. If a cryptocurrency wallet was linked, revoke any approvals granted to the site. Report the phishing page to Bloom Cosmetics and to your email or web security provider. Defenders should add bloomcosmeticsbeauty.shop to phishing blocklists, monitor DNS queries for the domain, and share indicators such as the IP address and TLS fingerprint with threat‑sharing communities.
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.
isaac.ns.cloudflare.comkay.ns.cloudflare.comLocation describes the IP network.
a831ba85e56b88d3e068eb7e0ffdbc8868c2b09de12d56b1ff014b698e90fabbSaved 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 bloomcosmeticsbeauty.shop · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bloomcosmeticsbeauty.shop/https://bloomcosmeticsbeauty.shop/Cache-Control: private, no-cache, no-store, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8summary_large_imageh3=":443"; ma=2592000private, no-cache, no-store, max-age=0, must-revalidategziptext/html; charset=utf-8Sat, 17 Oct 2026 20:46:41 GMT; rel=preload; as="style"strict-origin-when-cross-originchunkedRSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch, Accept-Encoding1.1 CaddynosniffSAMEORIGIN1; mode=blockValues 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
Unknown→live_content
content_served
1→2
Reachable
4 community references
View sourceNo threat flag
View source2/92 engine detections
View sourcePD-20261017-097AC9
bloomcosmeticsbeauty.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bloomcosmeticsbeauty.shop
PD-20261017-097AC9 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 ↗
bloomcosmeticsbeauty.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.