On 2026-10-01, s-fd0abdef62cdb9874e0edf7c.pages.dev returned HTTP status 502 during an HTTP check. The same record notes an IP address of 188.114.96.3, located in CA and associated with CloudFlare, Inc.
Recorded Evidence
The domain was first observed on 2026-09-07, and an internal listing was recorded as true. ScamSniffer was the single external blocklist entry counted on 2026-10-01. A VirusTotal check on 2026-09-17 recorded 3 detections across 89 scanners.
Interpretation
The HTTP check and blocklist count share the 2026-10-01 date, while the VirusTotal scan and first observation fall on earlier dates, so these records describe different moments rather than one simultaneous snapshot. ScamSniffer and the internal listing reflect separate listing sources, and their criteria may differ.
Recommended Actions
Reviewers should retain the dated records for s-fd0abdef62cdb9874e0edf7c.pages.dev and compare any later HTTP, blocklist, or VirusTotal observations against them. Until those comparisons are made, avoid submitting sensitive information to s-fd0abdef62cdb9874e0edf7c.pages.dev during review.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='s-fd0abdef62cdb9874e0edf7c.pages.dev', port=80): Max retries exceeded with url: / (Caused
Bitget Wallet - Best Crypto Wallet for Web3, DeFi, Safe & Fast
TLS 证书
Hostname coverage not recorded·
颁发者 YE2
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP 声誉不属于此域。
Location describes the IP network.
TLS 证书
Issuer
YE2
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:15:51 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-07 04:28:17 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.
Last analyzed First positive detection Previous stored snapshot: 3 detections
alphaMountain.ai
Forcepoint ThreatSeeker
VIPRE
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.
VirusTotal Detections Update2026-09-17 07:47:06 UTC
VirusTotal scanner detections updated from 0 to 3. Added scanner alerts: Forcepoint ThreatSeeker, VIPRE, alphaMountain.ai.
Domain Status Transition2026-09-15 22:00:15 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 12:03:10 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(US)
