sp29ct-zekun-biz-morvi-felak.pages.dev returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The same domain was first observed on 2026-09-17, so the recorded observation window spans roughly two weeks.
Recorded Evidence
The PhishDestroy internal listing records this domain as listed, with the listing checked on 2026-10-01. VirusTotal recorded 15 detections across 91 scanners on 2026-10-01, and the observation time for those detections is not known. The SSL certificate was scanned on 2026-09-21 and was issued by Google Trust Services / WE1. A PageSpeed check on 2026-09-23 returned a performance score of 66. The domain resolved to 172.66.44.52, associated with Cloudflare, Inc. in CA, per the recorded IP data.
Interpretation
The PhishDestroy listing and the VirusTotal scan were both checked on 2026-10-01, while the SSL scan and PageSpeed check carry earlier dates, so those observations describe different moments. The HTTP check and first-observed date bracket the listing and scan dates, which allows a reader to compare the sequence of records rather than treat them as one snapshot. Because the VirusTotal observation time is unknown, its detections cannot be tied to a specific moment within the recorded window.
Recommended Actions
Anyone reviewing sp29ct-zekun-biz-morvi-felak.pages.dev should retain the dated records, including the PhishDestroy listing and the VirusTotal result, in their original form. Subsequent checks should be compared against the 2026-10-01 HTTP status and the 2026-09-17 first observation to see whether the recorded state changes. During review, avoid submitting passwords, payment details, or other sensitive information to the domain until the records are independently verified.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: StaleRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 10:11:54 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 10:11:54 UTClast content: 2026-10-13 10:11:54 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: 16 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
MalwareURL
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of sp29ct-zekun-biz-morvi-felak.pages.dev· checked Sep 23, 2026
66
Needs Work
Performance
FCP
5.04s
First Contentful Paint
LCP
5.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
5.04s
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.
Threat First Observed2026-09-21 10:03:11 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
5 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.
