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

rstgov.info

“Token — RST”

Bureau d’enregistrement
Name.com
Resolved IP
64.29.17.65
Registered
16/08/2026
PhishDestroy assessment Critique
First observed Sep 6, 2026 16:40 UTC · PhishDestroy
Détections VirusTotal : 3/92
OTX: 4 refs 06/09/2026 CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 3. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Domain age
Résumé du rapport

Domaine sur listes de blocage: rstgov.info — Non vérifié. Résumé des preuves: VirusTotal 3/92 (alphaMountain.ai, Forcepoint ThreatSeeker, SOCRadar)…

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

Source evidenceVirusTotal 3 / 92 · OTX 4 references 4 sources

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

Analysis

Critique
VirusTotal
3 / 92
OTX
4 community refs

PhishDestroy threat report

Overview

rstgov.info is on the PhishDestroy blocklist. Its page carried the title "Token — RST", which presents it as the site of a crypto token called RST, and the "gov" in the name hints at a token-governance portal. PhishDestroy first saw it on 2026-09-06. As of 2026-10-19 the server still answered, but the domain's DNS no longer pointed to working content.

How the scam works

The page title and name show a token-branded site aimed at crypto holders. No specific scheme has been confirmed here. Sites that present a token or governance front are risky because they typically ask visitors to connect a wallet and then sign transactions or approvals. A single careless signature on such a page can hand control of tokens to a third party. Treat any prompt from this domain to connect, claim, vote or approve as a potential theft attempt.

Evidence

Four of 89 engines on VirusTotal flagged the domain as of 2026-09-19: Forcepoint ThreatSeeker, Gridinsoft, Netcraft and SOCRadar. That is a low count, but these vendors reached their verdicts independently, and Netcraft in particular tracks crypto phishing closely. The domain also appears in four AlienVault OTX threat pulses, which means other researchers have tied it to malicious activity. PhishDestroy is the only listed blocklist carrying it so far.

Infrastructure

The domain was registered through Name.com, Inc. on 2026-08-16, just 21 days before PhishDestroy picked it up. That short gap fits a site built for a brief campaign rather than a long-standing project. It was hosted on Amazon.com, Inc. infrastructure in the United States, at an address used by many unrelated customers. Blocking that address alone would be a blunt measure, so filter on the domain name instead.

What to do

If you connected a wallet to rstgov.info, review your token approvals with a trusted approval-checking tool and revoke any you granted to unfamiliar contracts. If you signed anything you did not fully understand, move your remaining assets to a fresh wallet. Never type a seed phrase into this or any similar "RST" site. If you only browsed the page without connecting or signing, no action is needed beyond avoiding it. Defenders should block the domain at DNS and proxy level and flag any mail or chat links that reference it.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domaine
IP Context Vercel shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement Name.com US(US)
Contact anti-abus["abuse@name.com"]
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 16/08/2026 (65d · New) — Expires 16/08/2027
Détails techniquesProvenance & timestamps
Première détection06/09/2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.29.17.65
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

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

Serveurs de noms 1

  • ns2.vercel-dns.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-08-16 04:02:16
Valid until
2026-11-14 04:02:15
Validity
Within stored validity dates
Collection time
2026-10-20 16:02:23 UTC
Collection source
PhishDestroy collector
Certificate fingerprint30fa6d4f98f60a79873c29b7de47dad16b2f5915ccc6a96f1754958f115ec958

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-20 08:21:37 UTC

Primary outcome DNS inactif reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Inconnu Probe Inconclusive 20% 2026-10-20 10:14:21 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-03 02:18:47 UTC current episode first observed: 2026-10-03 16:16:30 UTC observed RIP window: 2026-10-03 02:18:47 UTC → 2026-10-03 16:16:30 UTC · 13.96h midpoint estimate ≈ 2026-10-03 09:17:38 UTC · precision medium · 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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

3 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
Forcepoint ThreatSeeker
SOCRadar
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of rstgov.info · checked Sep 15, 2026

81
Needs Work
Performance
FCP
3.49s
First Contentful Paint
LCP
3.87s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.49s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
13.96
Estimate basis
Bounded by observations
Estimate precision
Moyen

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history19

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→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

Earlier observations 14
  1. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  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. VirusTotal · Detection count

    1→2

  14. Availability monitor · First collection record

    Accessible

Recorded activity

4 entries
  1. VirusTotal

    3/92 engine detections

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. Added to PhishDestroy

    rstgov.info

    View source

Renseignement communautaire

1 signalement communautaire

CatégorieRUG_PULL

Went to website rstgov.info. link on website led to Coinbase with option to buy RST tokens. believed in Coinbase to not allow scammers. Bought the token. as soon as token reached over 250%, it died. A new token with same name and wallet address appeared On Coinbase. ST3JuHB

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

rstgov.info

Données factuelles et rapports externes

Community Scam Report — ChainAbuse
1 report filed for rstgov.info (1 written by a person) · category: Rug Pull · source checked
“Went to website rstgov.info. link on website led to Coinbase with option to buy RST tokens. believed in Coinbase to not allow scammers. Bought the token. as soon as token reached over 250%, it died. A new token with same name and wallet address appeared On Coinbase. ST3JuHBDvuaVHLbgqznbrJbMD5bQedpvrhVK1icpump linked to a pumpfun account 9AEf9na5cs7auKuzwvFpCXdmqeJevoVc8Beims7xquVi”
— reported by Anonymous on Sep 6, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

2 evidence signal groups linked 0 stored notification records Non vérifié

Listed domains receive at least one abuse report; this entry has no retained notification history.

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 rstgov.info)
  • 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/rstgov.info"
  title="PhishDestroy threat report for rstgov.info"
  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>