VirusTotal
2 / 92 engine detections
Open report“Blush Me - The Premier Online Beauty Shop in Sri Lanka | Blush Me”
2 / 92 engine detections
Open reportMalicious
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
blushmeboutique.shop poses as Blush Me, a Sri Lankan online beauty retailer, to trick visitors into entering personal or payment details. The page title matches the legitimate brand’s storefront. PhishDestroy first detected the site on 2026-10-18. As of 2026-10-19, the page remains live and serving content.
The scam works by luring victims with a convincing replica of the Blush Me online storefront. Visitors are prompted to enter personal information or payment card details under the guise of completing a purchase. Once submitted, the data is harvested by attackers for fraud or resale. This impersonation phishing page exploits trust in the legitimate brand to steal sensitive information.
The site was flagged by 2 out of 92 VirusTotal engines on 2026-10-19, including detections from alphaMountain.ai and Gridinsoft. It appears in 3 OTX pulses and is listed on the PhishDestroy blocklist.
The domain resolves to an IP address in Georgia (62.233.61.10) hosted by Malakmadze Web LLC. The TLS certificate was issued by Let’s Encrypt under the identifier YE1.
Anyone who visited the site should avoid entering any personal or payment details. If you already submitted information, contact your bank or card issuer immediately to report potential fraud. Monitor accounts for unauthorized transactions and consider freezing affected cards. For defenders, block the domain and its IP at the network level and update blocklists to protect others.
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.
karl.ns.cloudflare.comLocation describes the IP network.
6b31f93d282fd009b2da454360e32eff162f097dae3cabae050631dd40c32414Saved 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 blushmeboutique.shop · checked Oct 18, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://blushmeboutique.shop/https://blushmeboutique.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-8Sun, 18 Oct 2026 03:30:59 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.
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 sourceblushmeboutique.shop
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
blushmeboutique.shop
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 ↗
blushmeboutique.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.