The domain bless.claims is a high-risk crypto drainer phishing site designed to steal cryptocurrency by tricking users into connecting their wallets. It impersonates Amazon and uses the Angel Drainer kit, a known malicious tool for draining wallet funds. As of the latest verification, bless.claims has been taken offline, but it remains a confirmed threat to users who may have interacted with it prior to its removal.
Technical indicators confirm the malicious nature of bless.claims. The domain was flagged by 1 of 95 security vendors on VirusTotal, including Gridinsoft, which assigned it a trust score of 0/100. It appears on 4 security blocklists: PhishDestroy, Polkadot, Enkrypt, and Codeesura. Registered through Web Commerce Communications Limited on August 15, 2025, the domain resolved to the IP address 172.67.196.159, hosted by Cloudflare in the US. No SSL certificate was issued, and the observed page title was 'Bless'. The domain was created recently, aligning with typical phishing campaign timelines.
Users who connected a wallet to bless.claims should immediately revoke all token approvals using a tool like Revoke.cash or Etherscan's token approval checker. Transfer remaining funds to a new, secure wallet to prevent further unauthorized access. Victims should also monitor their accounts for suspicious transactions and report the incident to their wallet provider and relevant authorities, such as the FBI's IC3 or local cybercrime units. If credentials were entered, change passwords immediately and enable two-factor authentication on all accounts.
DOM Analysisanalyzed 2026年4月23日score 98/1004 brand signals
Submitted URLhttps://bless.claims/
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.
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:16:35 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:17:50 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:50 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:22 UTC · precision 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.
Last analyzed Previous stored snapshot: 2 detections
Bfore.Ai PreCrime
Chong Lua Dao
Gridinsoft
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
353.95
Estimate basis
Bounded by observations
Estimate precision
Low
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='bless.claims', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
bless.claims
保存済みの結果
到達不能
Stored observation history12
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
あなたの仮想通貨取引所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
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.
(MY)
