The domain claimpayai.network was registered on February 21, 2026 through HOSTINGER operations, UAB and is presently taken offline. Evidence from multiple security sources indicates that the site was used as a crypto drainer, a variant of crypto‑scam infrastructure. The site presented a minimal HTTP response with the page title "Just a moment..." and did not deploy an SSL certificate, exposing all traffic to potential interception. Hosting is provided by Cloudflare, Inc. (AS13335) and resolves to the IPv4 address 172.67.213.224, which is geo‑located in the United States.
The domain appears on a single security blocklist and has been actively blocked by PhishDestroy, confirming its malicious intent. Reputation scoring from Gridinsoft assigns a trust score of 0 out of 100, effectively flagging the domain as highly untrustworthy. VirusTotal analysis shows that one of ninety‑three scanning engines flagged the domain, reinforcing the suspicion despite the low detection count. No additional metadata such as safe‑browsing or OTX indicators were provided.
Defensive teams should immediately add claimpayai.network and its resolving IP 172.67.213.224 to deny‑list configurations across perimeter firewalls, DNS filtering services, and endpoint protection solutions. Continuous monitoring of Cloudflare‑owned address space for related activity is advised, as attackers often reuse the same hosting provider for rapid redeployment. Given the lack of TLS, any future re‑activation would expose victims to clear‑text credential or wallet‑address capture, so intrusion‑prevention signatures that detect the specific page title "Just a moment..." or the absence of SSL on the domain should be incorporated. The combination of a fresh registration date, zero trust score, blocklist presence, and the single vendor flag constitutes a strong indicator of a malicious crypto‑draining operation, warranting proactive containment and ongoing intelligence collection.
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:08:12 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-04-21 22:27:32 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 22:27:32 UTC → 2026-09-30 16:14:55 UTC · 3,881.79hmidpoint estimate ≈ 2026-07-11 19:21:13 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='claimpayai.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
claimpayai.network
Stored observation history11
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)
