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.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='claimpayai.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
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-13 01:09:16 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(LT)
