VirusTotal
14 / 91 engine detections
فتح التقرير“relvadont.org | 522: Connection timed out”
تصيد: relvadont.org — لم يتم التحقق منها. ملخص الأدلة: VirusTotal 14/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker)…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
14 / 91 engine detections
فتح التقرير3 community references
فتح التقريرprovider verdict: clean
فتح التقريرNo threat flag
فتح التقريرNo malicious flag
فتح التقريرResults 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.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
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.
غير معروف→live_content
content_served
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→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.
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب
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.