Security engines reporting a detection: 12. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, migration-playzap-en.pages.dev returned an HTTP 403 status, indicating a restricted or denied response at that time. The domain is also listed on three external blocklists, which are MetaMask, ScamSniffer, and SEAL, based on separate source records.
Recorded Evidence
On 2026-10-01, migration-playzap-en.pages.dev was recorded with an HTTP 403 status. The domain appeared on MetaMask, ScamSniffer, and SEAL blocklists as of the blocklist check on the same date. VirusTotal reported 12 detections out of 89 scanners on 2026-09-09. The domain was first observed on 2026-08-28. A PageSpeed performance score of 90 and an SSL certificate issued by Google Trust Services / WE1 were recorded on 2026-09-08.
Interpretation
The presence of migration-playzap-en.pages.dev on multiple blocklists and the VirusTotal detections reflect separate evaluations by different sources, each using their own criteria and timing. The HTTP 403 status is a point-in-time response and does not describe the site's content or availability at other moments. These records together provide a timeline of observed responses and external listings for the domain.
Recommended Actions
For migration-playzap-en.pages.dev, retain the MetaMask, ScamSniffer, and SEAL blocklist records as well as the VirusTotal detection report and HTTP response for future comparison. Review each source's findings separately to monitor for changes or updates. Consult the latest records before interacting with the domain or referencing its status.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
IP ContextCloudflare shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerCloudflare Pages
HTTP Status403 Forbidden
Elapsed Since First Report11 days
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 28, 2026
Favicon Hash
Page Title
Suspected Phishing | Cloudflare
Impersonates
Cloudflare
TLS Certificate
Hostname coverage not recorded·
Issued by Google Trust Services· stored validity ends in 67 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.9
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-08-28 22:28:08 UTCcurrent episode first observed: 2026-10-01 01:33:56 UTCobserved RIP window: 2026-08-28 22:28:08 UTC → 2026-10-01 01:33:56 UTC · 795.10hmidpoint estimate ≈ 2026-09-14 12:01:02 UTC · precision very low · basis bounded
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.
Technologies · 3 identified
H
HSTS
Security
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Netcraft
Sophos
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of migration-playzap-en.pages.dev· checked Sep 8, 2026
90
Good
Performance
FCP
0.92s
First Contentful Paint
LCP
1.98s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
12.24s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-08 22:00:23 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-08 12:43:09 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
migration-playzap-en.pages.dev detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
3 evidence signal groups linked0 reports recordedReachable · access restricted
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches8
Same favicon hash or the same page title as this host.
