On 2026-10-01, the domain 64567d479ecd46d28a8cdc64b6adc408.pages.dev was recorded with an HTTP status 502, indicating a gateway error response at that time. The domain is also listed in the publisher-owned PhishDestroy internal catalogue, which is a distinct source observation.
Recorded Evidence
The domain was first observed on 2026-09-03. An HTTP check on 2026-10-01 returned a 502 status. VirusTotal checked the domain on 2026-09-13, recording 2 detections out of 89 scanners. The domain is listed in the PhishDestroy internal catalogue, and a blocklist check was performed on 2026-10-01.
Interpretation
Each source record provides a separate perspective on 64567d479ecd46d28a8cdc64b6adc408.pages.dev, with HTTP, VirusTotal, and PhishDestroy observations occurring on different dates. The HTTP response describes only the status recorded at the time of checking, while VirusTotal and PhishDestroy catalogue entries reflect their own measurement contexts. These records allow for comparison but do not establish a direct relationship between observations.
Recommended Actions
For 64567d479ecd46d28a8cdc64b6adc408.pages.dev, retain the HTTP status, VirusTotal detection count, and PhishDestroy listing as separate records. Review each source's findings individually and compare them for changes or consistency over time. Consider repeating the HTTP and VirusTotal checks to gather updated information for future assessment.
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.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='64567d479ecd46d28a8cdc64b6adc408.pages.dev', port=80): Max retries exceeded with url: / (C
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Domain details
Domain
Platform providerCloudflare Pages
Time to First Unavailability10 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
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 DetectedSep 3, 2026
Latest Classified Outcome 2026-10-11 01:14:28 UTC
Primary outcomeUnknownreason: Stale Current Evidence0% confidence
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:14:28 UTC
RDAP registrationUnknown
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.
Last analyzed First positive detection Previous stored snapshot: 2 detections
LevelBlue
PhishFort
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-12 22:00:27 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
64567d479ecd46d28a8cdc64b6adc408.pages.dev detected and queued for full analysis
Sep 3, 2026
Cloudflare Radar Report
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 latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 13, 2026
Time to First Unavailability
233 hours elapsed from detection to the first unavailable 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.
1 evidence signal groups linked0 reports recordedContent unavailable
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.
Same registrar: Cloudflare Pages6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
