URLQuery
2 det.
Open report“Soins pour cheveux bouclés naturels et boucles en pleine santé | Bouclème”
PhishDestroy threat report
PhishDestroy’s intake AI marked the site as malicious because it pretends to be the Bouclème brand and advertises a hair‑care product with a 70 % discount, a pattern typical of fake online stores. The page snapshot captured on 2026-10-27 showed the excerpt “Crème pour cheveux bouclés .63 .29‑70 %”, confirming the advertised discount. The domain was first observed by PhishDestroy on 2026-10-27, returning HTTP 200 after a 307 redirect from http to https. No external blocklists flagged the domain at that time.
Fake‑store scams copy a legitimate brand’s identity, display attractive discounts and a shopping interface, and then harvest payment details or personal information from unsuspecting buyers. Victims are typically lured into completing a purchase, at which point the operators collect the data and disappear without delivering any product.
VirusTotal scanned the domain on 2026-10-27 with 92 engines and reported 0 detections and 0 suspicious findings. Google Safe Browsing checked the site on the same day and did not flag it. URLScan captured the page on 2026-10-27 and gave an overall malicious verdict with a score of 100, categorising it as phishing and labeling it a fake shop. OTX listed 4 pulses mentioning the domain as of 2026-10-27. PhishDestroy’s internal blocklist includes the domain, while external blocklists returned a count of 0.
The domain was registered on 2026-04-16, giving it 193 days of age at the time of observation. It is hosted on IP 162.222.90.51 (ASN 199242, organization Malakmadze Web LLC, country GE) and uses Cloudflare nameservers bradley.ns.cloudflare.com and lana.ns.cloudflare.com. TLS is provided by Let’s Encrypt, issued on 2026-10-12 and valid until 2027-01-10. Open ports observed were 22, 80, 443 and 8000.
Users should avoid entering any personal or payment information on the site and should not proceed with any purchase. If credentials were submitted, change the associated passwords immediately. Defenders should block bouclemestore.shop at the DNS or proxy level, monitor for connections to 162.222.90.51, and add the domain to internal threat feeds.
2 det.
Open reportMalicious
SHA-256 e5796d408312c46036ff4597ca72e5005e00dc5c8de5c100258b4b5ca3d5498c
Observed: · Retrieved:
| Uuid | 01a17bfd-a4cd-75f4-8a35-7e0884e11709 |
|---|---|
| Final url | https://bouclemestore.shop/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://bouclemestore.shop/",
"from": "http://bouclemestore.shop/",
"status": 307
}
] |
| Ip | 162.222.90.51 |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.20.94",
"142.251.20.95",
"162.222.90.51"
] |
| Asns | [
"15169",
"199242"
] |
| Countries | [
"US",
"GE"
] |
| Document hash | e5796d408312c46036ff4597ca72e5005e00dc5c8de5c100258b4b5ca3d5498c |
| Script hashes | [
"7b7064487d9e49bda3b45855b6dbceeb3f17d94f311da2c689309f6b73078118",
"da1c9803523e7a18f5f93419f7dbf9cab702b5a78564eb9dc0e18c32e492ae4f",
"56bef185cd5d43be7d55db75e9756858e8a4093525595194b8d3202210013efe",
"2d9ed79eb6d7a824a49129543fe8712e46fdc8f048e145692492d81f589f33b5",
"5790cd3ddf6d13150fad9403a3be5269f8bb5c8905966746bca6929477b611e0",
"9de785ee19ccdf688f837e8bf8d2bbdb4c1dabc04b8ee7166bc1f4057226e49d",
"91eb4c6e12d5d0f37080b53c6a8b513c579db4854839928eb478164ef6dc1d65",
"acfed8ce931532ba4fbcdbc534468ab16b1e4ab08c8f8b9859558b9fbfc86d3e",
"54674023c15e7c7d2c117eacd9399f7e7ff4a224093be6fbd07fba4480b882ba",
"5594b2dc49c9ed560d32392288f138c9e3f4cccd2c8c71d305060cf653ce80c2"
] |
| Globals | [
"__next_f",
"webpackChunk_N_E",
"_N_E",
"next",
"_N_E_STYLE_LOAD",
"Prism"
] |
| Cookies | [
"_mx3_cid",
"_mx3_pv",
"_mx3_rg",
"_mx3_rid",
"_site_domain"
] |
| Storage keys | [
"analytics_session_id",
"analytics_session_id_ts",
"__analytics_utm__",
"analytics_visitor_id"
] |
| Tls | {
"san": [
"bouclemestore.shop"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "bouclemestore.shop",
"protocol": "TLS 1.3",
"valid_to": "2027-01-10T19:53:24Z",
"valid_from": "2026-10-12T19:53:25Z"
} |
| Domain age days | 193 |
| Apex age days | 193 |
| Tls age days | 14 |
| Tls valid days | 89 |
| Requests | 51 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 92,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"fakeshop"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Fake Shop"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"referrer-policy": "strict-origin-when-cross-origin"
} |
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
0 / 92 engine detections · stored summary
Open reportObserved: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 0,
"suspicious": 0,
"undetected": 37
} |
|---|---|
| Reputation | 0 |
| Created | 2026-04-16T00:00:00Z |
| Updated | 2026-04-16T00:00:00Z |
| First seen | 2026-04-16T17:33:24Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "lana.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "bradley.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "162.222.90.51"
},
{
"ttl": 21600,
"type": "NS",
"value": "bradley.ns.cloudflare.com"
}
] |
| Dns at | 2026-10-27T06:37:42Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"bouclemestore.shop"
],
"issuer": "Let's Encrypt / YE1",
"serial": "518c86f782b1b71d6115a34c65c6c6cd238",
"sha256": "743eb345ce64863c82ff15b1a9bd6bde81fb93f8b595be02c2f61db18ccec344",
"subject": "bouclemestore.shop",
"valid_to": "2027-01-10T19:53:24Z",
"valid_from": "2026-10-12T19:53:25Z"
} |
The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.
4 community references
Open reportprovider verdict: clean
Open reportObserved: · Retrieved:
| Uuid | dc439595-0e9b-45e1-bc1f-0dcad975b94b |
|---|---|
| Final url | https://bouclemestore.shop/ |
| Status | 200 |
| History | [
{
"url": "https://bouclemestore.shop/",
"status": 200
}
] |
| DOM structure hash | b88285ca2554439f01c7149b4743ff0d7102d004afd32a8aaf8fc135f569b61b |
| Document hash | 89e37797890f449d707d374b126a03676e5fbe583dfaa99e0c53fb45c753a550 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "bouclemestore.shop",
"type": "A",
"value": "162.222.90.51"
}
] |
| Dnssec valid | false |
| Ip | 162.222.90.51 |
No threat flag
Open reportCheck recorded; verdict not retained
Open report73 / 100 · heuristic score · 0 brand references · 1 classification
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "bouclemestore.shop"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_count": 0
} |
| Trackers | {
"requests": 48,
"trackers": [
{
"name": "Google Fonts",
"company": "Google",
"country": "US",
"category": "Hosting",
"requests": 1
},
{
"name": "Google Static",
"company": "Google",
"country": "US",
"category": "Hosting",
"requests": 1
}
]
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_128_GCM_SHA256",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
22,
80,
443,
8000
]
} |
| Dns server | {
"ns": [
{
"ip": "108.162.192.182",
"host": "lana.ns.cloudflare.com"
},
{
"ip": "172.64.35.35",
"host": "bradley.ns.cloudflare.com"
}
],
"zone": "bouclemestore.shop"
} |
| Location | {
"ip": "162.222.90.51",
"asn": "199242",
"org": "Malakmadze Web LLC",
"country": "GE"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE1",
"subject": "bouclemestore.shop"
} |
| DNS records | {
"A": [
"162.222.90.51"
],
"NS": [
"bradley.ns.cloudflare.com",
"lana.ns.cloudflare.com"
],
"SOA": "{\"nsname\": \"bradley.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417200843, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Get ip | {
"ip": "162.222.90.51",
"family": 4
} |
Checked, no match
Last checked
d7db525336ed99c1814e53be6cf4722d49ad5132deb15d9728b99d1ee465bed1 · 372959 bytes eca797e64dbe4d7c61652448d0777369004ac537ed0f564326e66dd203b2b09c · 257291 bytes 
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.
bradley.ns.cloudflare.comlana.ns.cloudflare.comnsname: bradley.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2417200843refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
743eb345ce64863c82ff15b1a9bd6bde81fb93f8b595be02c2f61db18ccec344bouclemestore.shopSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
img.bouclemestore.shopDomain recordGoogle PageSpeed Insights — mobile performance audit of bouclemestore.shop · checked Oct 27, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bouclemestore.shop/https://bouclemestore.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-8Tue, 27 Oct 2026 06:15:36 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.
live_content
content_served
Reachable
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
4 community references
View source0/92 engine detections
View sourcePD-20261027-6599E9 · Receipt 83831
bouclemestore.shop
View sourcePage captured
View sourceWe scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
bouclemestore.shop PD-20261027-6599E9 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.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Select your country to get official cybercrime contacts, or create a complaint draft →.
Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
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 ↗
bouclemestore.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.