VirusTotal
5 / 91 engine detections
فتح التقرير“securealliance.online”
نطاق في قوائم الحظر: securealliance.online — المحتوى غير متوفر. ملخص الأدلة: VirusTotal 5/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
5 / 91 engine detections
فتح التقريرno community references
فتح التقريرprovider verdict: clean
فتح التقرير80/100
فتح التقرير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
The domain securealliance.online was registered through Namecheap Inc on July 23, 2026 and remains active as of the report date, July 25, 2026. Authoritative name servers are dns1.registrar-servers.com and dns2.registrar-servers.com, indicating the registrar’s default infrastructure. DNS resolution points to the single IPv4 address 192.64.119.81. No additional hosting details such as ASN or geographic location are disclosed in the available data. Security telemetry shows the domain is associated with credential‑phishing activity.
It appears on one public blocklist and has been explicitly blocked by the PhishDestroy service, which corroborates the phishing classification. VirusTotal has recorded scans from 91 antivirus and URL‑reputation vendors; none have generated a detection at the time of analysis. Although the lack of detections does not imply benign intent, it does reflect that the sample has not triggered existing signatures. Public threat‑intel sources such as OTX, Google Safe Browsing, or similar reputation feeds do not currently list the domain, and no SSL certificate metadata, HTTP response codes, page title, or content snapshots have been published.
Consequently, the visual or functional characteristics of the site remain unknown, limiting attribution of the specific phishing lure. Given the recent creation date, active status, and confirmation by a dedicated anti‑phishing blocklist, defenders should treat securealliance.online as a high‑confidence phishing indicator. Network‑level controls should deny outbound connections to the resolved IP address 192.64.119.81, and email gateways should quarantine any messages containing URLs that resolve to this domain. Continuous monitoring of VirusTotal, blocklist updates, and any future host‑header or TLS observations is recommended to adjust the risk posture as additional evidence emerges.
Last checked
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.
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.
dns1.registrar-servers.comdns2.registrar-servers.comeforward3.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward1.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
يمكن الوصول إليه→غير متوفر
5/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcesecurealliance.online
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
securealliance.online
Listed 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 ↗
securealliance.online)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.