Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
polymarket.charity favicon

polymarket.charity

“polymarket.charity is registered at Namecheap”

Bureau d’enregistrement
Namecheap
Resolved IP
72.251.11.125
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 6/91 Spamhaus DBL: DBL_PHISH Correspondances de la liste de blocage stockée : 2 Type d'arnaque : Impersonation
OTX: 5 refs 30/06/2026 1 Report Sent
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 6. Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@namecheap.com. The latest stored availability evidence still shows the domain reachable; 3 months has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
3 months
Reports sent
1
Latest case ID
PD-20260630-A2FC94
Current status
HTTP 302 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
OTX
community references
Page captures
open gallery
Reports sent
view timeline
Résumé du rapport

Hameçonnage: polymarket.charity — Dernier actif connu (HTTP 302). Résumé des preuves: VirusTotal 6/91 (alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 6 / 91 · OTX 5 references 8 sources

Blocs DNS

3/14

Spamhaus DBL

DBL_PHISH

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Renseignements sur la sécurité réseau
DNS Provider Blocks 3 / 14
Controld Adblock Controld Family Controld Malware
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer:

Analysis

Critique
VirusTotal
6 / 91
OTX
5 community refs
Page captures
2

PhishDestroy threat report

This domain is flagged as a cryptocurrency wallet phishing site under active investigation. Analysis indicates it poses a high-risk threat to users of decentralized finance platforms, specifically targeting wallet credentials and private keys through fraudulent interfaces mimicking legitimate services. The domain exhibits characteristics of a credential harvesting operation, likely designed to exfiltrate sensitive financial data from unsuspecting victims. Infrastructure analysis reveals the following technical indicators: registered through NAMECHEAP INC on June 29, 2026, resolving to IP address 162.255.119.196. VirusTotal detection ratio stands at 0/95, suggesting the domain has not yet been widely flagged by security vendors. The domain was taken offline, but its recent creation date and lack of prior reputation indicate it was likely deployed for a short-term phishing campaign. No blocklist entries or trust scores were recorded at the time of assessment, further emphasizing its stealthy nature. Mitigation steps for this threat type include immediate blocking of the domain and associated IP address across all network security controls. Organizations should implement strict filtering rules for newly registered domains, particularly those using terms related to cryptocurrency or financial services. End users should be educated to verify domain authenticity through official sources and avoid entering wallet credentials on unfamiliar sites. Security teams are advised to monitor for connections to 162.255.119.196 and investigate any related network activity, as this may indicate compromise. Given the domain's recent creation and lack of detection, proactive hunting for similar infrastructure patterns is recommended.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Répertorié View source
PhishDestroy PhishDestroy list View source
SEAL Répertorié View source

Last checked

Capture enregistrée · 2 captures

Observed page title
polymarket.charity is registered at Namecheap

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
Réputation de l’IP abuse score 0/100 0 reports checked 29/09/2026
OTX tags 2026-06activeall-domainsblocklistcontentcryptodomainesdrainerfraudmonthlyphishdestroyphishingscam
Bureau d’enregistrement Namecheap IS(IS)
Contact anti-abusabuse@namecheap.com
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementExpires 29/06/2027
Statut HTTP302 Found (Temporary)
Détails techniquesProvenance & timestamps
Première détection30/06/2026
DOM Analysisanalyzed 11/07/2026score 95/100
Submitted URLhttp://polymarket.charity/
ID du dossier
ICANN OVERSIGHT

Contexte de l’accréditation et du 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.

Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
72.251.11.125
Network ASN
AS16276
Organization
AS22612 Namecheap, Inc.
Observed location
Los Angeles, US
Server header
nginx/1.28.3 (Ubuntu)

Serveurs de noms 2

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

Mail routing 5 MX records

  • eforward1.registrar-servers.compriority 10
  • eforward3.registrar-servers.compriority 10
  • eforward2.registrar-servers.compriority 10
  • eforward4.registrar-servers.compriority 15
  • eforward5.registrar-servers.compriority 20

Location describes the IP network.

Latest Classified Outcome 2026-10-19 22:27:14 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:27:14 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:27:14 UTC
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.
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

6 / Les fournisseurs de sécurité 91 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
Chong Lua Dao
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

redirect: raw=redirect_302; http=302; via=http_proxy; location=http://www.polymarket.charity/; server=namecheap-nginx

polymarket.charity
Résultat enregistré
Keitaro TDS
Stored observation history21

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Indisponible→Accessible

  4. Availability monitor · Recorded state

    Accessible→Indisponible

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Earlier observations 16
  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  13. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  14. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  15. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  16. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Recorded activity

6 entries
  1. AlienVault OTX

    5 community references

    View source
  2. VirusTotal

    6/91 engine detections

    View source
  3. URLScan

    Page captured

    View source
  4. Abuse report sent

    PD-20260630-A2FC94

    abuse@namecheap.com
  5. Google Safe Browsing

    No threat flag

    View source
  6. Added to PhishDestroy

    polymarket.charity

    View source

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260630-A2FC94 Recipient: abuse@namecheap.com
Page title stored with report: New Private Tab
Blocklist hits included with submission: MetaMask, SEAL
PDF notice generated Notice text archived (289 chars)
Abuse notice text as sent to the provider
Registrar: Namecheap Inc (United States)
Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

7 evidence signal groups linked 1 stored notification records Dernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

Template-based draft · optional AI wording assistance requires separate consent

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Que dois-je faire tout de suite ?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du FBI

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.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment polymarket.charity)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

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.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/polymarket.charity"
  title="PhishDestroy threat report for polymarket.charity"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>