VirusTotal
9 / 89 engine detections
レポートを開く“Meta for Business | Page Appeal”
フィッシング: 7t60y-ix3-chlx-vi11r-11-09-2026-hh.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 9/89 (alphaMountain.ai, BitDefender, Fortinet, G-Data…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 89 engine detections
レポートを開く15/100
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This throwaway Cloudflare Pages subdomain presented itself as "Meta for Business | Page Appeal", a form that page owners and advertisers would expect to use when contesting a restriction on their account. It is on the PhishDestroy blocklist, but no specific scheme type has been assigned to it yet. PhishDestroy first saw it on 2026-09-12. The site has been offline since 2026-09-13 because the provider blocked its content, and it was still dead when last checked on 2026-10-19.
Fake Meta appeal pages usually follow a warning that a business page is about to be disabled. The page then asks the visitor to sign in or submit details so they can contest the action. The page title points to this kind of lure, but the exact fields this site requested are not documented. The realistic risk for anyone who used it is the loss of their Facebook or Meta Business login and possibly their two-factor codes. That would give an attacker control of the page and any ad accounts linked to it.
VirusTotal shows 9 of 89 engines flagging the domain as of 2026-09-13. The flagging vendors include alphaMountain.ai, BitDefender, Fortinet, G-Data, Gridinsoft, Kaspersky, LevelBlue and Sophos. That count is modest, but these are independent vendors, and they flagged it within a day of PhishDestroy's detection. Apart from PhishDestroy's own listing, no other blocklist entries are documented.
The subdomain was created on 2026-09-10, two days before PhishDestroy detected it, and it was gone within one more day. Its random-looking string of characters is typical of disposable Cloudflare Pages deployments that can be published and abandoned quickly. Traffic was served from Cloudflare, Inc. address space geolocated to Canada. The free Let's Encrypt certificate meant the browser showed a padlock, which says nothing about whether the page could be trusted.
If you entered credentials on this page, change your Facebook password immediately and end all other active sessions. Reset two-factor authentication, and use an authenticator app rather than SMS where possible. In Meta Business settings, review the admins, partners and payment methods on your pages and ad accounts, and remove anyone you do not recognise. Remember that real Meta restriction notices appear inside your account's Business Support Home, not on outside sites. Defenders should block the domain and watch for similar randomly named pages.dev subdomains that carry Meta appeal titles.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
f249a3beb79bfabc3c47d540092b4a456112e7e39574864677ea80e5bf34f1f3Saved 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 7t60y-ix3-chlx-vi11r-11-09-2026-hh.pages.dev · checked Sep 13, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
7t60y-ix3-chlx-vi11r-11-09-2026-hh.pages.dev
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
8→9
到達可能→利用不可
No threat flag
View source9/89 engine detections
View source7t60y-ix3-chlx-vi11r-11-09-2026-hh.pages.dev
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 ↗
7t60y-ix3-chlx-vi11r-11-09-2026-hh.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.