VirusTotal
4 / 89 engine detections
فتح التقريرانتحال Google: zaywka-oon-oshad.lol — المحتوى غير متوفر. ملخص الأدلة: VirusTotal 4/89 (alphaMountain.ai, CRDF, Gridinsoft, SOCRadar); Google Safe Browsing…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
4 / 89 engine detections
فتح التقريرThreat flag recorded
فتح التقرير4 community references
فتح التقريرprovider verdict: clean
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
zaywka-oon-oshad.lol is an impersonation phishing page that poses as a trusted organisation to collect visitors' information. PhishDestroy first saw it on 2026-09-07, five days after the domain was registered. The site went offline on 2026-09-16 and was still dead with no active DNS on 2026-10-19.
Impersonation pages copy the look and wording of a legitimate service so visitors believe they are dealing with the real organisation. The visitor is usually told they must submit a form, an application or a verification step, and that step asks for names, phone numbers, login credentials, card details or one-time codes. Whatever is typed goes straight to the operators, who use it to take over accounts, make payments or contact the victim again with a more convincing follow-up scam.
Google Safe Browsing flagged the domain as social engineering, which is the category it uses for deceptive phishing pages and the reason many browsers showed a red warning. On VirusTotal, 4 of 89 engines rated it malicious as of 2026-09-17: alphaMountain.ai, CRDF, Gridinsoft and SOCRadar. That count is low, but it is typical for a short-lived page that most scanners never fetched while it was online. The domain also appears in 4 AlienVault OTX threat pulses and is listed on the PhishDestroy blocklist.
The domain was registered through Global Domain Group LLC on 2026-09-02, and the site was serving phishing content within five days. It stayed up for roughly nine days after we detected it and then went dark. A cheap .lol name used for a burst of about two weeks fits a disposable campaign, where operators expect takedowns and move on to new domains.
If you entered a password on this site, change it immediately, along with any other account that uses the same one, and turn on two-factor authentication. If you gave card or bank details, call your bank, block the card and dispute any charges you don't recognise. If you shared a one-time code or ID documents, tell the institution concerned and watch for follow-up calls or messages from people who claim to be its staff. Defenders should block the domain, search mail and proxy logs for visits between 2026-09-02 and 2026-09-16, and reset credentials for any users who reached the page.
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.
rommy.ns.cloudflare.comAn 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
2→4
يمكن الوصول إليه→غير متوفر
No flag recorded→Flag recorded
يمكن الوصول إليه
4 community references
View sourceThreat flag recorded
View source4/89 engine detections
View sourcezaywka-oon-oshad.lol
View sourceبلاغ مجتمعي واحد
الفئةPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-07T12:20:49.244Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
zaywka-oon-oshad.lol
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 ↗
zaywka-oon-oshad.lol)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.