VirusTotal
5 / 91 engine detections
فتح التقرير“404 Not Found”
نطاق في قوائم الحظر: forteckio.online — آخر نشاط معروف (HTTP 301). ملخص الأدلة: VirusTotal 5/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
5 / 91 engine detections
فتح التقرير4 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
The domain forteckio.online was registered through Namecheap Inc on 16 July 2026 and is currently resolving to the address 172.67.164.49. The authoritative name servers listed are alberto.ns.cloudflare.com and hazel.ns.cloudflare.com, indicating that the domain is hosted behind Cloudflare's edge network. As of the report date (21 July 2026) the domain remains active and is listed on a single public blocklist, where it is identified by PhishDestroy as a malicious phishing entry. VirusTotal has processed the domain with scans from 95 security vendors; at the time of analysis none of the vendors reported a detection, but the absence of a detection does not constitute a safety assurance. The rapid creation-to‑deployment timeline—registration on 16 July and active status by 21 July—matches typical patterns observed in opportunistic phishing campaigns that exploit newly minted domains to evade historical reputation. The use of Cloudflare’s DNS services provides basic DDoS mitigation and obscures the true origin of the hosting infrastructure, complicating attribution efforts. No SSL certificate details, HTTP response codes, or page title information have been disclosed, leaving the content of the site unverified. Given the limited public intelligence, the primary confidence indicators are the registrar record, the IP address association with Cloudflare, and the inclusion on PhishDestroy’s blocklist. Defenders should add forteckio.online to internal URL filtering and sink‑hole rules, monitor DNS queries for the listed Cloudflare name servers, and treat any traffic to the domain as potentially malicious. Continuous re‑scanning with VirusTotal or comparable multi‑engine services is advised to capture any future detections. Analysts should also query threat‑intel feeds such as OTX and Google Safe Browsing for updates, and consider requesting passive DNS data to track any future IP changes that may signal infrastructure migration.
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.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
alberto.ns.cloudflare.comhazel.ns.cloudflare.comLocation describes the IP network.
a58ada259a0c565eb6a6b1061509dd029fdc9c31ab770aef8831ee037590e105Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of forteckio.online · checked Jul 21, 2026
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.
forteckio.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
يمكن الوصول إليه→غير متوفر
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير متوفر→يمكن الوصول إليه
يمكن الوصول إليه→غير متوفر
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
4 community references
View source5/91 engine detections
View sourceNo threat flag
View sourceforteckio.online
View sourcePage captured
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 ↗
forteckio.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.