VirusTotal
4 / 92 engine detections
Open report“Home | Wholesale Body Jewellery”
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; 29 hours 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.
4 / 92 engine detections
Open report2 det.
Open reportMalicious
Open reportno 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
PhishDestroy has added bodyjewelleryhub.shop to its internal blocklist as a suspicious domain. The recorded page title is “Home | Wholesale Body Jewellery”. The domain was first observed by PhishDestroy on 2026-10-20.
The current evidence does not identify a specific malicious mechanism for this site. Listings based on heuristic detections may indicate phishing, fraud, or malware risk, but no concrete behavior has been observed on this page.
VirusTotal reported 4 detections from 92 scanning engines, with alerts from alphaMountain.ai, CRDF, G-Data and Gridinsoft; the scan was retrieved on 2026-10-20 and analyzed on 2026-10-15. Google Safe Browsing reported no threat as of 2026-10-20, external blocklists showed zero matches, PhishDestroy’s internal list flagged the domain, and OTX listed zero pulses on the same date.
The only recorded network detail is the IP address 62.233.61.26 that resolved when the site was examined. No registrar, CDN, certificate, or additional hosting information is available in the current data.
Avoid entering personal or financial information on this site and monitor any accounts for unexpected activity. Defenders should add a rule to block traffic to bodyjewelleryhub.shop in firewalls or proxy filters and review logs for any prior accesses.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a15ab8-5f9e-7237-969a-8ad10a057442 |
|---|---|
| Final url | https://bodyjewelleryhub.shop/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://bodyjewelleryhub.shop/",
"from": "http://bodyjewelleryhub.shop/",
"status": 307
}
] |
| Ip | 62.233.61.26 |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.45.195",
"142.251.16.95",
"62.233.61.26"
] |
| Asns | [
"15169",
"199242"
] |
| Countries | [
"US",
"GE"
] |
| Document hash | 8fe442d6c3b13857c701adf92b698a6d91197a5b2c3eef1892c97a06c7429a8e |
| Script hashes | [
"0122728f4b95ab7dde22c6691221e73adc3033a9635f6b670d0e09725105f9d5",
"da1c9803523e7a18f5f93419f7dbf9cab702b5a78564eb9dc0e18c32e492ae4f",
"56bef185cd5d43be7d55db75e9756858e8a4093525595194b8d3202210013efe",
"2d9ed79eb6d7a824a49129543fe8712e46fdc8f048e145692492d81f589f33b5",
"91eb4c6e12d5d0f37080b53c6a8b513c579db4854839928eb478164ef6dc1d65",
"acfed8ce931532ba4fbcdbc534468ab16b1e4ab08c8f8b9859558b9fbfc86d3e",
"5790cd3ddf6d13150fad9403a3be5269f8bb5c8905966746bca6929477b611e0",
"54674023c15e7c7d2c117eacd9399f7e7ff4a224093be6fbd07fba4480b882ba",
"ef598e4df04d2d336c9267057130a0ab7a499d928810f0bceb6393f28a5fcb03",
"915eca2ddd30cf0f0dcf655424d66e36e55d66a038b3365bfff815980b355c29"
] |
| Globals | [
"__next_f",
"webpackChunk_N_E",
"next",
"_N_E_STYLE_LOAD",
"Prism"
] |
| Cookies | [
"_l10_cid",
"_l10_rg",
"_l10_rid",
"_site_domain"
] |
| Storage keys | [
"analytics_session_id",
"analytics_session_id_ts",
"__analytics_utm__",
"analytics_visitor_id"
] |
| Tls | {
"san": [
"bodyjewelleryhub.shop"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "bodyjewelleryhub.shop",
"protocol": "TLS 1.3",
"valid_to": "2027-01-09T09:03:36Z",
"valid_from": "2026-10-11T09:03:37Z"
} |
| Domain age days | 129 |
| Apex age days | 129 |
| Tls age days | 9 |
| Tls valid days | 89 |
| Requests | 56 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 95,
"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"
} |
Observed: · Retrieved:
| Uuid | 622b591c-c25b-442c-863c-0857a315cb0c |
|---|---|
| Final url | https://bodyjewelleryhub.shop/ |
| Status | 200 |
| History | [
{
"url": "https://bodyjewelleryhub.shop/",
"status": 200
}
] |
| DOM structure hash | 8ec92e04382ee51b85a269371b9851d8d18af13150352093790250ed1181044f |
| Document hash | c65a6c0342b7387e7e2798a0c17beb11c247c264cb26eddbd6ad16b5796451cc |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "bodyjewelleryhub.shop",
"type": "A",
"value": "62.233.61.26"
}
] |
| Dnssec valid | false |
| Ip | 62.233.61.26 |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 52,
"malicious": 2,
"suspicious": 2,
"undetected": 36
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"G-Data": "malware",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "suspicious"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Suspicious (alphaMountain.ai)"
} |
| First seen | 2026-06-13T12:07:29Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "62.233.61.26"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "megan.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "osmar.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "megan.ns.cloudflare.com"
}
] |
| Dns at | 2026-10-15T21:14:27Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"bodyjewelleryhub.shop"
],
"issuer": "Let's Encrypt / YE1",
"serial": "59f0b4f30fcffea48ed3c4b8c9cdc45519",
"sha256": "37cfda4568992bf1200c1502cf333114c740370e80f39865f7a7838721f6739a",
"subject": "bodyjewelleryhub.shop",
"valid_to": "2027-01-09T09:03:36Z",
"valid_from": "2026-10-11T09:03:37Z"
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "bodyjewelleryhub.shop"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_count": 0
} |
| 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": "173.245.58.197",
"host": "megan.ns.cloudflare.com"
},
{
"ip": "108.162.195.124",
"host": "osmar.ns.cloudflare.com"
}
],
"zone": "bodyjewelleryhub.shop"
} |
| Location | {
"ip": "62.233.61.26",
"asn": "199242",
"org": "Malakmadze Web LLC",
"country": "GE"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE1",
"subject": "bodyjewelleryhub.shop"
} |
| DNS records | {
"A": [
"62.233.61.26"
],
"NS": [
"osmar.ns.cloudflare.com",
"megan.ns.cloudflare.com"
],
"SOA": "{\"nsname\": \"megan.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417043158, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Get ip | {
"ip": "62.233.61.26",
"family": 4
} |
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.
megan.ns.cloudflare.comosmar.ns.cloudflare.comLocation describes the IP network.
37cfda4568992bf1200c1502cf333114c740370e80f39865f7a7838721f6739aSaved 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 bodyjewelleryhub.shop · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bodyjewelleryhub.shop/https://bodyjewelleryhub.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:12:39 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
Unknown→live_content
content_served
Reachable
No threat flag
View sourcePD-20261020-DFCBA7
4/92 engine detections
View sourcebodyjewelleryhub.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bodyjewelleryhub.shop
PD-20261020-DFCBA7 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 ↗
bodyjewelleryhub.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.