pages-app-a2f.pages.dev shows a static page headed "Cloudflare Pages" with a rocket emoji. The visible text states the page is served by Cloudflare Pages and that the button below calls a Pages Function at /api/hello — server-side code running on Cloudflare's edge with no separate backend to deploy.
URLScanによるキャプチャ · 2026-10-19 10:43 UTC · SHA-256 147f34cd…3475c3a
PhishDestroyの分析(レビュー済み版)
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
pages-app-a2f.pages.dev shows a static page headed "Cloudflare Pages" with a rocket emoji. The visible text states the page is served by Cloudflare Pages and that the button below calls a Pages Function at /api/hello — server-side code running on Cloudflare's edge with no separate backend to deploy.
An orange button labeled "Call /api/hello" sits beneath the text, followed by a light output box displaying the placeholder "Click the button...". The page presents a simple demonstration of invoking an edge function from a static page, with no other visible content or interactions.
pages-app-a2f.pages.dev: Cloudflare Pages Function demo page
AIによる説明
PhishDestroy records pages-app-a2f.pages.dev as a static Cloudflare Pages demo with a button calling a Pages Function at /api/hello.
AIによる要約
pages-app-a2f.pages.dev shows a static page headed "Cloudflare Pages" with a rocket emoji. The visible text states the page is served by Cloudflare Pages and that the button below calls a Pages Function at /api/hello — server-side code running on Cloudflare's edge with no separate backend to deploy. An orange button labeled "Call /api/hello" sits beneath the text, followed by a light output box displaying the placeholder "Click the button...". The page presents a simple demonstration of invoking an edge function from a static page, with no other visible content or interactions.
エビデンスレイヤーAvailability: Content servingContent: Content served at rootDNS: Stale
最新のHTTP観測結果コンテンツ公開中通常のHTTPコンテンツが配信される90%2026-11-22 11:22 UTC
RDAP登録
観測されたタイムラインlast reachable: 2026-11-22 11:22 UTClast content: 2026-11-22 11:22 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.