VirusTotal
4 / 92 engine detections
Відкрити звіт“Uw Juwelierszaak in Den Haag & Amsterdam | Bodes & Bode Juweliers”
домен у блоклистах: bodemuse.shop — Останній відомий активний (HTTP 200). Зведення доказів: VirusTotal 4/92 (CRDF, G-Data, Gridinsoft, Netcraft); URLQuery 2…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
4 / 92 engine detections
Відкрити звіт2 det.
Відкрити звітno community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітPage capture
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has added bodemuse.shop to its internal blocklist as a suspicious domain. The site’s recorded title advertises a jewelry business in The Hague and Amsterdam. The domain was first seen by PhishDestroy on 2026-10-20.
Because the domain is flagged without a known scam type, the exact malicious behavior cannot be determined. Suspicious domains may be used for phishing, fraud, or malware distribution, but no evidence of such activity was observed on this page.
VirusTotal scanned the domain on 2026-10-18 and reported 4 detections out of 92 engines, with CRDF, G-Data, Gridinsoft and Netcraft flagging it. Google Safe Browsing checked on 2026-10-20 and did not flag the URL. No external blocklists listed the domain as of 2026-10-20, while PhishDestroy’s internal list marked it as suspicious on the same date. OTX had zero pulses referencing the domain on 2026-10-20.
The recorded IP address for bodemuse.shop is 62.106.90.117. No registrar or certificate details are available in the current data. This information applies only to the observed address and does not identify the operator.
Visitors should not enter personal or financial information on the site. If any credentials were entered, change them immediately. Organizations should add the domain to blocklists and monitor logs for connections to 62.106.90.117.
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.
dalary.ns.cloudflare.comluke.ns.cloudflare.comLocation describes the IP network.
3f7050ade332c97812c6280476dd0b9fa0b709aac6e8024a848e6e1e8de47462Saved 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 bodemuse.shop · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bodemuse.shop/https://bodemuse.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, 20 Oct 2026 19:06:08 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.
Доступний
PD-20261020-C4BE37
No threat flag
View source4/92 engine detections
View sourcebodemuse.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bodemuse.shop
PD-20261020-C4BE37 Recipient: abuse@rashost.com Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
bodemuse.shop)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.