Aller au rapport de sécurité
Domain security report
redotpaycn.com favicon

redotpaycn.com

“红豆钱包(RedotPay)中国官方网站 - 数字支付与综合金融服务”

Verdict de menace
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Correspondances de la liste de blocage stockée : 2 Automated brand label: MetaMask Domaine jeune : 10 jours
16/10/2026 MetaMask 1 Report Sent CDN
API
Bureau d’enregistrement
GMO Internet Group
Resolved IP
188.114.96.3
Registered
07/10/2026
2 sources
Redirect recorded in the HTML archive→ www.redotpaycn.comView the dated response and saved headers
In this reportGet help
Ce domaine a été signalé comme malveillant
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 · 24H+ 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@internet.gmo. The latest stored availability evidence still shows the domain reachable; 27 hours 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
27 hours
Reports sent
1
Latest case ID
PD-20261016-EEC49C
Current status
HTTP 301 at latest stored check
Résumé du rapport

redotpaycn.com — Dernier actif connu (HTTP 301). Usurpation de l'identité de la marque : MetaMask; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 0/92; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 75/100. Bureau d’enregistrement: GMO Internet Group.

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

Additional indicators at a glance

URLScan
URLScan
Certificat TLS
Within stored validity dates
Let's Encrypt / YE2 · Hostname coverage not recorded
Âge
10d Very New!
Statut observé
Dernier actif connu 301
PhishDestroy
DestroyList
Répertorié
Reports Sent
1

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

Public blocklists

2 external matches

Détails
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

VirusTotal

checked — no detections recorded

Signaler
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Signaler
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

no community references

Signaler
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: suspicious

Observation time not recorded
Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

rapport stocké

View stored capture ↗
Signaler
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analyse terminée

Signaler
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Résumé des preuves

Critique
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

The domain redotpaycn.com was observed with a PhishDestroy internal listing on 2026-10-16, which is a notable entry in the security context. On the same date, a PageSpeed check recorded a performance score of 55 for this domain, providing insight into its technical profile.

Recorded Evidence

On 2026-10-16, redotpaycn.com appeared on two external blocklists: MetaMask and SEAL. VirusTotal checked the domain on 2026-10-16 and reported 0 detections out of 92 total scanners. The registrar for redotpaycn.com is recorded as GMO Internet Group, Inc. d/b/a Onamae.com, with a registration date of 2026-10-07. A PageSpeed performance score of 55 was documented on 2026-10-16.

Interpretation

PhishDestroy's internal listing for redotpaycn.com contains a record of the domain as of 2026-10-16, which is a type of security intelligence measurement. VirusTotal's scan provides a snapshot of how many detection engines flagged the domain at a specific point in time. The MetaMask and SEAL blocklist entries further add to the external context, each representing a separate evaluation by a security source. These records together offer a multi-faceted view of the domain's presence in various security monitoring systems.

Recommended Actions

For ongoing monitoring of redotpaycn.com, retain the PhishDestroy, MetaMask, and SEAL blocklist records for future comparison. Preserve the VirusTotal detection results as a reference point for any subsequent changes in scanner findings. Comparing future PageSpeed scores may also help track technical changes to the domain over time.

Data coverage & collection

24 · datasets with records / 7 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
0 / 92 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
2 · external matches
Cloudflare Radar
suspiciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
GMO Internet Group, Inc. d/b/a Onamae.comCollection time not recorded
Network & DNS
188.114.96.3 · 2 · nameserversCollection time not recorded
Certificat TLS
Let's Encrypt / YE2
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
55/100 · mobile performance
Response records
1 · outgoing report records
Availability history
2 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 7

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Recorded subdomains
  • Signalements communautaires
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Statut de la liste de blocage publique

Domain, network & archive

GMO Internet Group, Inc. d/b/a Onamae.com · 188.114.96.3 · DNS, TLS and retained responses

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
Bureau d’enregistrement GMO Internet Group
Contact anti-abusabuse@internet.gmo
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 07/10/2026 (10d · Very New!) — Expires 07/10/2027
Statut HTTP301 Moved Permanently
Détails techniquesProvenance & timestamps
Première détection16/10/2026
DOM Analysisanalyzed 16/10/2026score 75/100
Submitted URLhttp://redotpaycn.com/
Favicon Hash
ID du dossier

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 2
  • joyce.ns.cloudflare.com
  • mustafa.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YE2
Valid from
2026-10-07 12:20:55
Valid until
2027-01-05 12:20:54
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 16:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb6059c46075a09fe313f04a672ae275b27337ee6d9bfbdf518b122b6119e5ba2

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-17 10:00: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-17 10:00:14 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-17 10:00: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.
Recoupement des renseignements sur les menaces · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
Technologies · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of redotpaycn.com · checked Oct 16, 2026

55
Needs Work
Performance
FCP
2.61s
First Contentful Paint
LCP
63.71s
Largest Contentful Paint
CLS
0.167
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
10.41s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://redotpaycn.com/
Final URL: http://www.redotpaycn.com/
红豆钱包(RedotPay)中国官方网站 - 数字支付与综合金融服务
红豆钱包(RedotPay)中国官方网站聚焦数字支付与综合金融服务,围绕数字钱包、支付服务、账户管理、卡片服务及多元应用场景持续完善业务体系。RedotPay依托数字技术与金融科技服务能力,为用户提供便捷、高效的数字化支付体验,持续拓展全球支付场景与综合服务能力。
Réponse
HTTP 200
HTML body
143.1 KB
Compressed
35.0 KB
Links
119 internal · 5 external
Detected technologies
jqueryvuebootstrapcloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
X-Powered-By: Nginx
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
alt-svc
h2=":443"; ma=60
cf-cache-status
DYNAMIC
CF-RAY
a4b7b5dbe818dcca-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 14:21:31 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=TP3zW%2BrnVhoLIq4r4RYj1CmGZmXMZPFC4csVYZKna68Pc67orP%2BhnMDoS8LmZ9%2BSgmG5eTNlvr4NCYB%2BdXsuVrLpsr7Cw64stoeg9NI7T3SI4uK%2FRSBV2Yah9o5veJZYKf7lr
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding
X-Powered-By
Nginx

Values retained by the collector; long values may be shortened during collection.

Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Reachable (legacy)
/robots.txt
HTTP response
200
Observed at
2026-10-16 14:21:32 UTC
Source
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-16 14:21:32 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Reachable (legacy)
/.well-known/security.txt
HTTP response
200
Observed at
2026-10-16 14:21:32 UTC
Source
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

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.

Detection & evasion checks

Stored browser and crawler observations

Analyse de la détection et de l'évasion

Vérification du cloaking et de la répartition du trafic

Pas encore numérisé Aucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée

Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.

Indicateur de camouflage enregistré
Pas encore numérisé
Dernier scan de camouflage
En-tête du serveur détecté par le scanner
cloudflare
Routage de la capture
Local archivé le 2026-10-16 14:21:32 UTC

Note relative à la numérisation: redirect: raw=redirect_301; http=301; via=https_proxy; location=http://www.redotpaycn.com/; server=cloudflare

Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro et une comparaison entre navigateur et robot. Une nouvelle analyse démarre uniquement en cliquant sur le bouton.
À la demande

Aucun résultat de vérification enregistré.

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
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.
  1. Threat First Observed 2026-10-16 14:21:50 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
Stored observation history3

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 · First collection record

    Inconnu

  3. Availability monitor · Recorded state

    Inconnu

    probe_inconclusive

Processus de réponse aux menaces Pipeline

Découverte
Analysis
Notifications
Monitoring

10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Menace détectée
redotpaycn.com détectés et mis en file d'attente en vue d'une analyse complète
16/10/2026
URLScan.io Capture
Enregistré URLScan report with capture artifacts
16/10/2026
Cloudflare Radar Report
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 Wayback Machine — historical evidence archived
17/10/2026
Détection des listes noires
Trouvé dans 2 blocklists: MetaMask, SEAL
17/10/2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
16/10/2026
Technical Analysis Recorded
Le rapport contient des résultats de technologie ou d’analyse médico-légale stockés.
17/10/2026
Sent Report Recorded
Stored outgoing record associated with registrar GMO Internet Group, Inc. d/b/a Onamae.com, 1 abuse contact
abuse@internet.gmo
16/10/2026
DestroyList publié
16/10/2026
Monitoring Continues
Le domaine reste accessible ou restreint en accès ; des contrôles futurs pourraient mettre à jour cette 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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Related infrastructure

Shared hosting, registrar records and related domains

Domaines ressemblants

79 domaines ressemblants enregistrés

Tout afficher (67)
metasmask.io insertion Rapport interne metramask.io insertion Rapport interne mewtamask.io insertion Rapport interne mmetamask.io homoglyph Rapport interne mtamask.io omission Rapport interne mwetamask.io insertion Rapport interne nmetamask.io homoglyph Rapport interne metamark.io bitsquatting Rapport interne metamaskj.io addition Rapport interne metammask.io homoglyph Rapport interne metamnask.io homoglyph Rapport interne emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20261016-EEC49C Recipient: abuse@internet.gmo
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
Référencement naturel et nom de domaine
Analyse approfondie

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Ce site vous a-t-il affecté ?

4 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 redotpaycn.com)
  • 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
Read the evidence in context

À propos de ce rapport : redotpaycn.com

Ce rapport présente les dernières preuves stockées disponibles pour PhishDestroy. Les horodatages sources sont affichés lorsqu'ils sont disponibles ; la disponibilité et les verdicts des fournisseurs peuvent changer après la collecte.

Le site capturé affichait le titre de la page “红豆钱包(RedotPay)中国官方网站 - 数字支付与综合金融服务” et usurpait peut-être l'identité de MetaMask.

PhishDestroy répertorie redotpaycn.com comme suspect. Il a été vérifié par les moteurs de sécurité 92 ; les verdicts automatisés peuvent changer. La surveillance se poursuit. Observé: 2026-10-16 14:21:59 UTC

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A 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/redotpaycn.com"
  title="PhishDestroy threat report for redotpaycn.com"
  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>