VirusTotal
7 / 89 engine detections
فتح التقرير“Meta | Community Standards Violation”
انتحال Facebook: facebook-verify-fanpage.com — المحتوى غير متوفر. ملخص الأدلة: VirusTotal 7/89 (alphaMountain.ai, BitDefender, ESET, G-Data, Gridinsoft)…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
7 / 89 engine detections
فتح التقرير2 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
facebook-verify-fanpage.com is a phishing page that impersonates Facebook and its parent company Meta. It targets people who run Facebook fan pages and business pages. The page presented itself as "Meta | Community Standards Violation", which is the kind of warning page admins dread. PhishDestroy first detected it on 2026-09-10. The site has been offline since 2026-09-18, and its DNS was still inactive when we checked again on 2026-10-19.
This scheme relies on fear of losing a page. The victim gets a message saying their fan page broke Community Standards and will be restricted or deleted unless they verify ownership. The link leads to a page dressed in Meta branding that asks for the Facebook login, and often the two-factor code as well. Whatever is typed in goes straight to the operators, who use it to take over the account and the pages it controls. Hijacked pages are then commonly resold or used to run fraudulent ads and further scams.
On 2026-09-12, VirusTotal showed 7 of 89 engines flagging the domain: alphaMountain.ai, BitDefender, ESET, G-Data, Gridinsoft, SOCRadar and desenmascara.me. That is a minority of engines, but it includes several established security vendors who reached the same verdict independently. The domain also appears in 2 AlienVault OTX threat pulses, so other researchers tracked it too. Among blocklists, PhishDestroy listed it.
The domain was registered through Name.com, Inc. on 2026-09-08, just two days before PhishDestroy caught it. That short gap is typical of throwaway phishing domains built for one campaign. It was hosted on Amazon's AMAZON-02 network in the US at 216.198.79.1. The site used a free Let's Encrypt certificate, so the browser padlock only meant the connection was encrypted. It said nothing about who was running the page.
If you entered your Facebook password on this page, change it right away and also change it anywhere else you reuse it. Then review Meta's active sessions and log out every device you don't recognize. Turn on two-factor authentication with an authenticator app, and check that no unknown admins were added to your pages or Business Manager. If you can no longer log in, use Meta's hacked-account recovery flow. Remember that Meta does not send appeal links through direct messages or comments. Defenders should block the domain and flag lookalike domains combining "facebook", "verify" or "fanpage" in mail and web filters.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
dns1.p08.nsone.netdns2.p08.nsone.netdns3.p08.nsone.netdns4.p08.nsone.netLocation describes the IP network.
1e6e3476adcaba0f47571cef02218962fe543d3312eb0f2510190ccd88bfeae2Saved 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.
facebook-verify-fanpage.com
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
No threat flag
View source7/89 engine detections
View source2 community references
View sourcefacebook-verify-fanpage.com
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 ↗
facebook-verify-fanpage.com)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.