Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
bonheuratelier.shop favicon

bonheuratelier.shop

In short

bonheuratelier.shop is a blocklisted domain detected by PhishDestroy on 2026-10-24.

“Bonheur Jewelry | Bonheur”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
United States195.96.130.210Malakmadze Web LLC
Registered
May 23, 2026
First observed
Oct 24, 2026
PhishDestroy assessment Critical
78/100
Evidence score
First observed Oct 24, 2026 21:45 UTC · PhishDestroy
Risk signals
VirusTotal detections: 5/92
VirusTotal
5 / 92
engine detections ·
URLScan
Malicious
Page captures
4
open gallery
Domain age
158 days
Oct 24, 2026
X Telegram API

Analysis

Domain summary

bonheuratelier.shop is a blocklisted domain detected by PhishDestroy on 2026-10-24. Risk: critical (78/100). Registrar: Dynadot. Hosting: Malakmadze Web LLC. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
5 / 92
Hosting
United States195.96.130.210Malakmadze Web LLC
Registrar
United StatesDynadot
Registered
May 23, 2026
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added bonheuratelier.shop to its internal blocklist on 2026-10-24 after an automated URLScan analysis returned a malicious verdict. The recorded page title reads "Bonheur Jewelry | Bonheur", which suggests a retail storefront. The intake system noted a prior clean AI assessment but the URLScan result overrode that assessment, leading to the current listing.

How the scam works

The domain is categorized as a fake online shop that could be used to harvest personal or payment information by mimicking a legitimate jewelry retailer. Such sites typically present product listings and checkout flows to lure visitors into submitting credit‑card details or login credentials, without delivering any goods. No specific evidence of credential capture or payment processing was observed on this page, but the phishing classification reflects the general risk associated with counterfeit e‑commerce fronts.

Evidence

URLScan (captured 2026-10-07, retrieved 2026-10-24) reported a malicious verdict with a score of 100, labeling the site as phishing and assigning it to the "Fake Shop" brand. VirusTotal (analysis 2026-10-11, retrieved 2026-10-24) flagged the domain on five engines: three malicious (CRDF, G-Data, Netcraft) and two suspicious (Gridinsoft, alphaMountain.ai). Google Safe Browsing checked on 2026-10-24 did not flag the URL. OTX listed zero pulses as of 2026-10-24. No external blocklists reported the domain, but PhishDestroy’s internal list marks it as blocked.

Infrastructure

The recorded IP was 195.96.130.210 and the hosting organization was listed as Malakmadze Web LLC in the United States. TLS is provided by a Let's Encrypt certificate valid from 2026-09-19 to 2026-12-18. The domain was registered 137 days prior to the report and uses Cloudflare nameservers (macy.ns.cloudflare.com, ned.ns.cloudflare.com). Open ports observed include 22, 80, 443, and 8000, and DNSSEC is not enabled.

What to do

Visitors should avoid entering any personal, login, or payment information on the site and, if they have already done so, change affected passwords and monitor financial accounts. Defenders should block traffic to bonheuratelier.shop, log any connections, and apply the same block to future resolutions of the domain. No wallet‑related actions are required as no crypto‑wallet activity was detected.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-24T21:49:49Z)VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 5 / 92 8 sources

VirusTotal

5 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
3
Suspicious
2
Undetected
34

Vendor labels

CRDF
malicious
G-Data
malware
Netcraft
malicious
Gridinsoft
suspicious
alphaMountain.ai
suspicious

Reputation score

0

Categories

alphaMountain.ai
Suspicious (alphaMountain.ai)

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    macy.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    195.96.130.210
  • TTL, seconds
    21600
    Type
    NS
    Value
    ned.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    macy.ns.cloudflare.com

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • bonheuratelier.shop
Issuer
Let's Encrypt / YE2
Serial
6dce7e58d54dea461886d67d0c037ef483
SHA-256
bf926ef8085ff87069fdc2fa54c1238e1594c8047a83cbadd2bca4990147c9bf
Subject
bonheuratelier.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 3,
    "suspicious": 2,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "G-Data": "malware",
    "Netcraft": "malicious",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "suspicious"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Suspicious (alphaMountain.ai)"
}
First seen
2026-05-23T01:09:01Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "macy.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "195.96.130.210"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ned.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "macy.ns.cloudflare.com"
    }
]
Dns at
2026-10-11T17:35:15Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "bonheuratelier.shop"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "6dce7e58d54dea461886d67d0c037ef483",
    "sha256": "bf926ef8085ff87069fdc2fa54c1238e1594c8047a83cbadd2bca4990147c9bf",
    "subject": "bonheuratelier.shop",
    "valid_to": "2026-12-18T08:13:21Z",
    "valid_from": "2026-09-19T08:13:22Z"
}
Separate source record · 3 malicious + 2 suspicious / 92 · 2026-10-11 15:54:19 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-11T15:54:19Z
fetched_at
2026-10-24T21:48:59Z
stats
{"timeout":0,"harmless":53,"malicious":3,"suspicious":2,"undetected":34}

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a16ff9-408c-77f9-ade7-e6633cdea276

Final URL

https://bonheuratelier.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://bonheuratelier.shop/
    From
    http://bonheuratelier.shop/
    Status
    307

IP address

195.96.130.210

Contacted domains

  • fonts.gstatic.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.250.195.99
  • 172.217.25.170
  • 195.96.130.210

Autonomous systems (ASN)

  • 15169
  • 199242

Server countries

  • US

Document hash

a55dd657de5df96655a9e656cc8fa7e5c88923fe101d0e37a4e9fc593e1203e1

Script hashes

  • 99aa2906d3df518ea7f23bd73833385c045487e1264a983aba7128bd3b93f555
  • da1c9803523e7a18f5f93419f7dbf9cab702b5a78564eb9dc0e18c32e492ae4f
  • 56bef185cd5d43be7d55db75e9756858e8a4093525595194b8d3202210013efe
  • 2d9ed79eb6d7a824a49129543fe8712e46fdc8f048e145692492d81f589f33b5
  • 5790cd3ddf6d13150fad9403a3be5269f8bb5c8905966746bca6929477b611e0
  • 9de785ee19ccdf688f837e8bf8d2bbdb4c1dabc04b8ee7166bc1f4057226e49d
  • 91eb4c6e12d5d0f37080b53c6a8b513c579db4854839928eb478164ef6dc1d65
  • acfed8ce931532ba4fbcdbc534468ab16b1e4ab08c8f8b9859558b9fbfc86d3e
  • 54674023c15e7c7d2c117eacd9399f7e7ff4a224093be6fbd07fba4480b882ba
  • 5594b2dc49c9ed560d32392288f138c9e3f4cccd2c8c71d305060cf653ce80c2

JavaScript globals

  • __next_f
  • webpackChunk_N_E
  • next
  • _N_E_STYLE_LOAD
  • Prism

Cookies

  • _kgm_cid
  • _kgm_pv
  • _kgm_rg
  • _kgm_rid
  • _site_domain

Browser storage keys

  • analytics_session_id
  • analytics_session_id_ts
  • __analytics_utm__
  • analytics_visitor_id

TLS session and certificate

Subject alternative names
  • bonheuratelier.shop
Cipher
AES_128_GCM
Issuer
YE2
Subject
bonheuratelier.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

154

Registered domain age, days

154

Certificate age, days

35

Certificate validity, days

89

Page requests

48

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
94
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • fakeshop
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Fake Shop
Malicious
Yes
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
Original source fields · JSON
Uuid
01a16ff9-408c-77f9-ade7-e6633cdea276
Final url
https://bonheuratelier.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://bonheuratelier.shop/",
        "from": "http://bonheuratelier.shop/",
        "status": 307
    }
]
Ip
195.96.130.210
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.250.195.99",
    "172.217.25.170",
    "195.96.130.210"
]
Asns
[
    "15169",
    "199242"
]
Countries
[
    "US"
]
Document hash
a55dd657de5df96655a9e656cc8fa7e5c88923fe101d0e37a4e9fc593e1203e1
Script hashes
[
    "99aa2906d3df518ea7f23bd73833385c045487e1264a983aba7128bd3b93f555",
    "da1c9803523e7a18f5f93419f7dbf9cab702b5a78564eb9dc0e18c32e492ae4f",
    "56bef185cd5d43be7d55db75e9756858e8a4093525595194b8d3202210013efe",
    "2d9ed79eb6d7a824a49129543fe8712e46fdc8f048e145692492d81f589f33b5",
    "5790cd3ddf6d13150fad9403a3be5269f8bb5c8905966746bca6929477b611e0",
    "9de785ee19ccdf688f837e8bf8d2bbdb4c1dabc04b8ee7166bc1f4057226e49d",
    "91eb4c6e12d5d0f37080b53c6a8b513c579db4854839928eb478164ef6dc1d65",
    "acfed8ce931532ba4fbcdbc534468ab16b1e4ab08c8f8b9859558b9fbfc86d3e",
    "54674023c15e7c7d2c117eacd9399f7e7ff4a224093be6fbd07fba4480b882ba",
    "5594b2dc49c9ed560d32392288f138c9e3f4cccd2c8c71d305060cf653ce80c2"
]
Globals
[
    "__next_f",
    "webpackChunk_N_E",
    "next",
    "_N_E_STYLE_LOAD",
    "Prism"
]
Cookies
[
    "_kgm_cid",
    "_kgm_pv",
    "_kgm_rg",
    "_kgm_rid",
    "_site_domain"
]
Storage keys
[
    "analytics_session_id",
    "analytics_session_id_ts",
    "__analytics_utm__",
    "analytics_visitor_id"
]
Tls
{
    "san": [
        "bonheuratelier.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "bonheuratelier.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-18T08:13:21Z",
    "valid_from": "2026-09-19T08:13:22Z"
}
Domain age days
154
Apex age days
154
Tls age days
35
Tls valid days
89
Requests
48
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "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 monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1176f-baf2-77c0-baba-efef25cff216
score
null
malicious
null
result_at
null
enriched_at
2026-10-26T09:21:16Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-26 10:21:16"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

49757ad9-89bd-4d45-8ad8-f0bc5f112d59

Final URL

https://bonheuratelier.shop/

HTTP response

200

Navigation history

  • URL
    https://bonheuratelier.shop/
    Status
    200

DOM structure hash

f732a36f54ba813892678509bce2806d861c2bb291109e104a52b9590316c601

Document hash

c0c09d9f7b4d91e11d7dd2103136aacf43a2270533cefd90ab59120f9a26e32b

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    bonheuratelier.shop
    Type
    A
    Value
    195.96.130.210

DNSSEC valid

No

IP address

195.96.130.210
Original source fields · JSON
Uuid
49757ad9-89bd-4d45-8ad8-f0bc5f112d59
Final url
https://bonheuratelier.shop/
Status
200
History
[
    {
        "url": "https://bonheuratelier.shop/",
        "status": 200
    }
]
DOM structure hash
f732a36f54ba813892678509bce2806d861c2bb291109e104a52b9590316c601
Document hash
c0c09d9f7b4d91e11d7dd2103136aacf43a2270533cefd90ab59120f9a26e32b
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "bonheuratelier.shop",
        "type": "A",
        "value": "195.96.130.210"
    }
]
Dnssec valid
false
Ip
195.96.130.210

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

78 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-24T22:05:58Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-24T22:05:58Z
source_timestamp
2026-10-25 00:05:58
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
bonheuratelier.shop — Suspicious Domain
ai_description
PhishDestroy flagged bonheuratelier.shop as suspicious after URLScan labeled it malicious, noting a fake‑shop appearance.
ai_generated_at
2026-10-24T21:51:46Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 12 fields

Mail configuration

SPF lookups
0

CAA records

Domain
bonheuratelier.shop

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Trackers

Requests
42
Observed services
  • 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
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443
  • 8000

DNS servers

Nameservers
  • IP address
    108.162.193.210
    Host
    ned.ns.cloudflare.com
  • IP address
    108.162.194.78
    Host
    macy.ns.cloudflare.com
DNS zone
bonheuratelier.shop

Location

IP address
195.96.130.210
ASN
199242
Organization
Malakmadze Web LLC
City
Los Angeles
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
bonheuratelier.shop

DNS records

A
  • 195.96.130.210
NS
  • macy.ns.cloudflare.com
  • ned.ns.cloudflare.com
SOA
Primary nameserver
macy.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2415177624
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
195.96.130.210
IP version
4
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "bonheuratelier.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Trackers
{
    "requests": 42,
    "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.193.210",
            "host": "ned.ns.cloudflare.com"
        },
        {
            "ip": "108.162.194.78",
            "host": "macy.ns.cloudflare.com"
        }
    ],
    "zone": "bonheuratelier.shop"
}
Location
{
    "ip": "195.96.130.210",
    "asn": "199242",
    "org": "Malakmadze Web LLC",
    "city": "Los Angeles",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "bonheuratelier.shop"
}
DNS records
{
    "A": [
        "195.96.130.210"
    ],
    "NS": [
        "macy.ns.cloudflare.com",
        "ned.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"macy.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2415177624, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "195.96.130.210",
    "family": 4
}

Questions about bonheuratelier.shop

Is bonheuratelier.shop legit?

No. PhishDestroy classifies bonheuratelier.shop as a blocklisted domain (risk: critical, 78/100); it was first detected on 2026-10-24. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.

Is bonheuratelier.shop safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on bonheuratelier.shop. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used bonheuratelier.shop?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)
Observed page title
Bonheur Jewelry | Bonheur
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 51 days
bonheuratelier.shop: caution — 5/92 VirusTotal engines. PhishDestroy risk score 78/100 (critical).
Social preview card bonheuratelier.shop: caution — 5/92 VirusTotal engines. PhishDestroy risk score 78/100 (critical). v 14b2dde3a52b

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Fakeshop report ↗
IP Reputation United States195.96.130.210 abuse score 2/100 1 report PhishingBad Web Bot checked Oct 25, 2026 last reported
Registrar Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for bonheuratelier.shop →
RegistrationCreated May 23, 2026 (158d) — Expires May 23, 2027
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 25, 2026score 78/100
Submitted URLhttp://bonheuratelier.shop/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States195.96.130.210
Network ASN
AS199242
AS name
malakmadze Malakmadze Web LLC, GE
Organization
Malakmadze Web LLC
Observed location
United StatesLos Angeles, US

Nameservers 2

  • macy.ns.cloudflare.com
  • ned.ns.cloudflare.com

SOA

  • nsname: macy.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2415177624
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-19 08:13:22
Valid until
2026-12-18 08:13:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbf926ef8085ff87069fdc2fa54c1238e1594c8047a83cbadd2bca4990147c9bf
Certificate names · 1 SAN
  • bonheuratelier.shop

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 195.96.130.210rapiddns.io

Latest Classified Outcome 2026-10-27 11:26:19 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-27 11:26:19 UTC
RDAP registration
Observed timeline last reachable: 2026-10-25 23:21:41 UTC last content: 2026-10-25 23:21:41 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
CRDF
G-Data
Gridinsoft
Netcraft

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of bonheuratelier.shop · checked Oct 24, 2026

68
Needs Work
Performance
FCP
2.89 s
First Contentful Paint
LCP
8.04 s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
77 ms
Total Blocking Time
SI
4.51 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations11

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.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:26:19.000000
    Evidence SHA-256
    fb08a40efe7853aa2bc7b84c865def60149c3041a3d2eadecf06de6cbd8e7316
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:26:19
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:26:19.000000
    Evidence SHA-256
    fb08a40efe7853aa2bc7b84c865def60149c3041a3d2eadecf06de6cbd8e7316
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:26:19
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:19:23.000000
    Evidence SHA-256
    e24419bd5b1191a948e7c95e48002c696cd02227ea514b3da806740d6f0349b4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:19:23
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:19:23.000000
    Evidence SHA-256
    e24419bd5b1191a948e7c95e48002c696cd02227ea514b3da806740d6f0349b4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:19:23
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:21:41.000000
    Evidence SHA-256
    7ee296347b47b9e6f36828b9758b0612b7fd4081f5fabc10f2aff4ab7b75688f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:21:41
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:21:41.000000
    Evidence SHA-256
    7ee296347b47b9e6f36828b9758b0612b7fd4081f5fabc10f2aff4ab7b75688f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:21:41
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:19:18.000000
    Evidence SHA-256
    3ddda2055b8fd7c46723884031431bcbe651ebe3507b6bafdb33389088f0ff11
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:19:18
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:19:18.000000
    Evidence SHA-256
    3ddda2055b8fd7c46723884031431bcbe651ebe3507b6bafdb33389088f0ff11
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:19:18
    Evidence reason
    alive_content
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:07:50.000000
    Evidence SHA-256
    75341ff5e1b67c9729f8e2517c1190fd8bb513ab6cb6a41edb0492b850cf611d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:07:50
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:07:50.000000
    Evidence SHA-256
    75341ff5e1b67c9729f8e2517c1190fd8bb513ab6cb6a41edb0492b850cf611d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:07:50
    Evidence reason
    alive_content
  11. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 23:52:50.283982
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    bonheuratelier.shop detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 5/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

4 entries
  1. URLScan

    Page captured

    View source
  2. Wayback Machine

    Page archived

    View source
  3. VirusTotal

    5/92 engine detections

    View source
  4. Added to PhishDestroy

    bonheuratelier.shop

    View source
How we investigate & report

Public scans, evidence and abuse channels

We 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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

bonheuratelier.shop

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 5 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Unverified
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select 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.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including bonheuratelier.shop)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/bonheuratelier.shop"
  title="PhishDestroy threat report for bonheuratelier.shop"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>