VirusTotal
6 / 92 engine detections
打开报告“Bling King | High-Quality 9CT”
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; 2 days 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.
钓鱼: blingkingldn.shop — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 6/92 (alphaMountain.ai, CRDF, ESET, Gridinsoft, Netcraft); URLScan malicious verdict…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 92 engine detections
打开报告恶意
打开报告Scan report
打开报告3 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
blingkingldn.shop presents itself as a jewelry retailer, using the page title “Bling King | High-Quality 9CT” to suggest authentic precious‑metal goods. The page is aimed at consumers looking to purchase 9‑carat items, often paying with cryptocurrency. PhishDestroy first recorded the domain on 2026-10-17. As of the last check on 2026-10-19 the site remains live and serves the same fraudulent content.
The fraudulent storefront lists attractive 9CT jewelry at discounted prices and directs buyers to a payment page that typically requests crypto transfers. After a victim sends funds, the site provides no order confirmation or shipping details, effectively disappearing with the payment. The page title reinforces a legitimate‑sounding brand, while the underlying kit simply serves static product pages and a crypto‑payment form.
VirusTotal flagged the domain in 6 out of 92 scanning engines, with detections from alphaMountain.ai, CRDF, ESET, Gridinsoft, Netcraft and SOCRadar, indicating broad security‑vendor consensus. urlscan.io returned a malicious verdict and specifically marked the site as a fake shop. The domain is already listed on PhishDestroy’s blocklist and appears in three OTX pulses, further confirming malicious activity.
The domain was registered on 2026-06-12 through Dynadot Inc., roughly four months before PhishDestroy’s first sighting. Hosting is provided by Malakmadze Web LLC in Georgia (GE) on IP 62.233.61.10. The site uses a Let’s Encrypt / YE1 TLS certificate, which is common for legitimate sites but does not mitigate the fraudulent content.
Anyone who entered personal details or sent cryptocurrency should cease all payments, monitor the wallet for unauthorized activity, and consider moving remaining funds to a new address. Change passwords on any accounts where credentials were used and enable two‑factor authentication. Report the incident to the relevant exchange or payment provider. Security teams should block blingkingldn.shop at the network perimeter, add it to internal threat feeds, and monitor for similar fake‑shop patterns in other domains.
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.
demi.ns.cloudflare.comkarl.ns.cloudflare.comLocation describes the IP network.
c0ddb4a44da2bfae11e3c862998ad3457f62a03e2fccfb677d1c6ca2e437ffc1Saved 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 blingkingldn.shop · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://blingkingldn.shop/https://blingkingldn.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-8Sat, 17 Oct 2026 20:21:02 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy
blingkingldn.shop
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
不可用→可访问
可访问→不可用
5→6
未知→live_content
content_served
未知→redirected
http_redirect
No threat flag
View source3 community references
View source6/92 engine detections
View sourcePD-20261017-8159B9
Page captured
View sourceblingkingldn.shop
View sourcePD-20261017-8159B9 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 ↗
blingkingldn.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
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.