VirusTotal
14 / 91 engine detections
Ouvrir le rapport“relvadont.org | 522: Connection timed out”
Hameçonnage: relvadont.org — Non vérifié. Résumé des preuves: VirusTotal 14/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker)…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
14 / 91 engine detections
Ouvrir le rapport3 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
relvadont.org is an impersonation phishing site. It is built to pass itself off as a legitimate service so that visitors trust it with their credentials or crypto. PhishDestroy first logged it on 2026-09-19. As of 2026-10-19 the domain still resolves, but its content does not load. A domain that stays live with an empty front end can be repointed at a working phishing page at any moment, so treat it as active.
Impersonation pages copy the look, wording and login flow of a brand people already trust. A visitor usually arrives through a link in a message, ad or social post and assumes they are on the real site. Anything typed into the fake forms goes straight to the operators. That can include account passwords, one-time codes, recovery phrases or private keys, and with those the attacker can take over accounts or empty wallets. When last captured, the page title read "522: Connection timed out", a Cloudflare error. That error page differs from the impersonation content we classified the site for.
On 2026-10-02, 14 of 91 VirusTotal engines flagged the domain. That is a meaningful minority for a site serving no visible content. The vendors include ADMINUSLabs, alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. The domain also appears in three AlienVault OTX threat pulses, so other researchers have tracked it independently. Among blocklists it is currently listed by PhishDestroy.
The domain was registered through NameCheap, Inc. on 2026-02-13, about seven months before PhishDestroy detected it. That long gap fits a domain held in reserve or used quietly before drawing attention. Traffic is served through Cloudflare, Inc. on an address geolocated to Canada. Cloudflare sits in front of the real server, which hides where the phishing content is actually hosted.
Do not visit relvadont.org or follow links pointing to it. If you entered a password there, change it on the genuine service and anywhere you reused it. Then enable app-based two-factor authentication and review recent logins. If you typed a recovery phrase or private key, consider that wallet compromised and move your funds to a new wallet created on a clean device. Security teams should block the domain at DNS and proxy level, search mail and chat logs for links to it, and report it to Cloudflare and NameCheap for takedown.
La réputation Edge-IP n’est pas attribuée à ce domaine.
giancarlo.ns.cloudflare.comeforward3.registrar-servers.compriority 10eforward1.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
0f50f6e454f4df91db6a9ea4e3336a4042ba0feb9b0d42a6faabc14a65fd9fedSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
relvadont.org
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→live_content
content_served
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
No threat flag
View source14/91 engine detections
View source3 community references
View sourcerelvadont.org
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
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 ↗
relvadont.org)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.