ABUSE NOTICE · 72H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 3 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.
PhishDestroy’s automated assessment labels blueoceanprojecthq.shop as an E‑Commerce scam, describing it as a fake online shop. The page title captured on 2026‑10‑18 reads “Blue Ocean Project | Blue Ocean Project”. The site returned an HTTP 200 response when checked on 2026‑10‑20.
How the scam works
Fake online‑shop scams present a storefront that appears legitimate, advertise products, and then collect payment details or funds without delivering anything. Victims are typically asked to pay via credit cards, bank transfers, or cryptocurrency, after which the operators disappear with the money. The scheme relies on the illusion of a real e‑commerce site to harvest personal and financial information.
Evidence
VirusTotal scanned the domain on 2026‑10‑11 and found 6 detections from 92 engines, flagged by alphaMountain.ai, CRDF, G‑Data, Gridinsoft, LevelBlue and Netcraft, while urlscan.io captured the page on 2026‑10‑18 and marked it malicious with a “fakeshop” label. Google Safe Browsing checked on 2026‑10‑19 and did not flag the site; PhishDestroy’s internal blocklist lists the domain as of 2026‑10‑19, while Spamhaus DBL reported no listing on 2026‑10‑18. OTX noted four pulses referencing the domain on 2026‑10‑19.
Infrastructure
The domain was registered on 2026‑05‑19 through Dynadot Inc., 152 days before PhishDestroy first observed it on 2026‑10‑18. The recorded IP address is 23.252.79.184, associated with the network “malakmadze Malakmadze Web LLC, GE” located in Georgia. A TLS certificate issued by Let’s Encrypt / YE2 was observed on 2026‑10‑18.
What to do
Do not enter personal, payment or credential information on the site and report the URL to your organization’s security team. If any payment details were submitted, contact the relevant financial institution to dispute the transaction. Defenders should add blueoceanprojecthq.shop to block lists, monitor outbound traffic for connections to 23.252.79.184, and review logs for any access attempts on or after 2026‑10‑18.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-21 10:33:21 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-21 10:33:21 UTClast content: 2026-10-21 10:33:21 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.
技术 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
