On 23 July 2026, a technical assessment was performed on the domain cloud-dropx.online. The domain was registered on 23 May 2025 through Hostinger Operations UAB and resolves to the IPv4 address 45.67.136.10, which belongs to autonomous system AS213535 operated by YottaSrc in the Netherlands. The site presented an SSL certificate identified as R13, indicating the presence of a publicly trusted TLS layer. The page title returned by the server at the time of capture was “Boba Network – Claim Airdrop”, and the underlying kit has been classified as an “Airdrop Scam” kit, a known vector for crypto‑related phishing campaigns. The domain is explicitly marked as impersonating the Metamask brand, aligning with the declared crypto‑scam type.
Detection telemetry shows that one of ninety‑three security vendors on VirusTotal flagged the domain as malicious. The host is listed on five independent blocklists, including PhishDestroy, ScamSniffer, Polkadot, Enkrypt and Codeesura, reinforcing the consensus that the infrastructure is being used for illicit activity. Independent reputation services assigned a Gridinsoft trust score of 0 out of 100, the lowest possible rating, indicating a high confidence of malicious intent. The current operational status is “offline”, suggesting that the site has been taken down or is otherwise inaccessible. No live HTTP response or page content was available for further forensic analysis, so the exact phishing landing page structure and any credential‑harvesting mechanisms remain unknown.
However, the combination of a brand‑impersonation tag, a crypto‑airdrop lure, a low trust score, and multiple blocklist entries provides sufficient evidence for defensive actions. Defenders should immediately add cloud-dropx.online to network‑level deny lists, update URL filtering policies, and monitor DNS traffic for queries to the associated IP address and ASN.
DOM Analysisanalyzed 2026年3月24日score 63/1003 brand signals
ICANN OVERSIGHT
認定と RAA の背景
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:08:06 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-27 16:22:26 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-27 16:22:26 UTC → 2026-09-30 16:14:55 UTC · 3,023.87hmidpoint estimate ≈ 2026-07-29 16:18:40 UTC · precision very low · basis bounded
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='cloud-dropx.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
cloud-dropx.online
保存済みの結果
到達不能
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
詐欺による金銭の返還を装った詐欺 — 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.
(LT)
