VirusTotal
1 / 93 engine detections
Ouvrir le rapportDomaine sur listes de blocage: claimpayai.network — Contenu indisponible. Résumé des preuves: VirusTotal 1/93 (SOCRadar); PhishDestroy score 61/100. Bureau…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
1 / 93 engine detections
Ouvrir le rapportchecked — no detections recorded
Ouvrir le rapportno community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapportNo threat flag
Ouvrir le rapportNo malicious flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
La réputation Edge-IP n’est pas attribuée à ce domaine.
Location describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
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
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/c5fca92c-24de-44e3-875c-400e9aa6641e
No threat flag
View source1/93 engine detections
View sourceclaimpayai.network
View sourcePD-1767766457-claimpayai.netw
Page captured
View sourcePD-1767766457-claimpayai.netw Recipient: abuse@hostinger.com Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
claimpayai.network)Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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.