VirusTotal
13 / 89 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Cloudflare: rpcaccessresolve.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 13/89 (alphaMountain.ai, BitDefender…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
13 / 89 engine detections
فتح التقريرضار
فتح التقريرThreat flag recorded
فتح التقريرno community references
فتح التقريرNo malicious flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
rpcaccessresolve.pages.dev is an impersonation phishing page that borrowed Cloudflare's branding to win the trust of visitors. PhishDestroy first saw it on 2026-09-09. The site has been offline since 2026-09-17, its content blocked by the hosting provider, and it was still dead at the last check on 2026-10-19.
Brand-impersonation pages like this copy the look and wording of a trusted service, then ask the visitor to sign in, verify an account or follow a fix-it step. Whatever is typed in, such as login credentials, one-time codes or tokens, goes straight to the operator. The subdomain name suggests a lure about resolving RPC access problems. The page title reads "Suspected Phishing | Cloudflare", which is Cloudflare's own phishing warning, while we classify the site itself as an impersonation of Cloudflare.
On 2026-09-18, VirusTotal showed 13 of 89 engines flagging the domain. The vendors included alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft, Fortinet, G-Data and Google Safe Browsing. Google Safe Browsing labels it SOCIAL_ENGINEERING, the category browsers use to warn users before they reach deceptive pages. That is a moderate detection rate, but it comes from several unrelated security vendors, and PhishDestroy lists the domain on its blocklist.
The subdomain was created on Cloudflare Pages on 2026-08-25, about two weeks before PhishDestroy detected it. That kind of quick turnaround is typical of disposable phishing sites. It resolved to Cloudflare, Inc. network space geolocated in Canada. A brand impersonation hosted on the impersonated company's own free platform inherits a legitimate-looking address and certificate, which is why the hostname alone is no proof of authenticity.
If you entered a password on this page, change it at once and sign out all other sessions. Then reset or re-enroll two-factor authentication. Revoke any API tokens or keys you may have pasted, and review recent account activity for changes you did not make. Use the same reset steps anywhere the same password was reused. Defenders should block the domain and alert on lookalike Pages subdomains that use support or troubleshooting wording.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
8d60850bb860628a323790594ed3d6e0ac6eeb3fe1c0b56142f4c4adabf8bd45Saved 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 rpcaccessresolve.pages.dev · checked Sep 16, 2026
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.
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
11→13
يمكن الوصول إليه→غير متوفر
No flag recorded→Flag recorded
يمكن الوصول إليه
Threat flag recorded
View source13/89 engine detections
View sourcerpcaccessresolve.pages.dev
View source١٤٢ نطاقًا متشابهًا محفوظًا
عرض 100 من 142
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
rpcaccessresolve.pages.dev
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 ↗
rpcaccessresolve.pages.dev)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.