Security engines reporting a detection: 10. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
According to Tranco this site has a low rank We tried to analyze the content of the site but failed
Evidence Summary
Critical
VirusTotal
10/95
URLScan
Stored capture
The domain claims-quant.network has been identified as a crypto_drainer, a specialized threat designed to siphon cryptocurrency assets from compromised wallets. As of the latest assessment, the domain is offline, but prior activity indicates it was actively used to deploy malicious scripts targeting users of decentralized finance platforms. No legitimate brand impersonation has been confirmed, though the infrastructure aligns with known crypto theft operations. Analysis indicates that claims-quant.network was flagged by 10 of 95 security vendors on VirusTotal, reflecting a consensus on its malicious nature. The domain resolves to the IP address 172.67.142.218, hosted under AS13335 (Cloudflare, Inc.), and was registered through the same provider. It appears on two security blocklists, including PhishDestroy and ScamSniffer, further validating its classification as a high-risk asset. The domain lacks an SSL certificate, a common red flag for fraudulent sites, and its page title, 'Just a moment...,' suggests the use of evasion techniques to delay or obscure detection. Current status confirms that claims-quant.network has been taken offline, likely due to enforcement actions or infrastructure changes by the threat actor. However, the domain’s prior activity and associations with crypto-draining scripts warrant continued vigilance. Organizations and individuals are advised to block the domain and its resolving IP (172.67.142.218) at the network level. Wallet providers should monitor for interactions with this domain in transaction logs and alert users who may have engaged with it. Proactive measures, such as updating endpoint protection rules and educating users on recognizing crypto-drainer tactics, are recommended to mitigate residual risk.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 28, 2025
DOM Analysisanalyzed Apr 11, 2026score 78/100
Submitted URLhttps://claims-quant.network/
ICANN OVERSIGHT
Accreditation and RAA context
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 inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:08:18 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-04-21 20:03:44 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 20:03:44 UTC → 2026-09-30 16:14:55 UTC · 3,884.19hmidpoint estimate ≈ 2026-07-11 18:09:19 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.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
claims-quant.network detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Feb 23, 2026
Time to First Unavailability
3541 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
5 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · claims-quant.network
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: Cloudflare6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(US)
