On 2026-10-01, feat-edit-competition.dydx-trading-competition-frontend-production.pages.dev returned an HTTP 403 status code according to a recorded check. The domain was first observed on 2026-08-26, and a PageSpeed check on 2026-09-01 gave a performance score of 99.
Recorded Evidence
The HTTP check on 2026-10-01 recorded a 403 response. On the same date, the blocklist check showed listings on MetaMask and SEAL. VirusTotal, checked on 2026-09-02, reported 12 detections from 91 scanners. An internal listing was also recorded.
Interpretation
The observations from MetaMask, SEAL, and VirusTotal each represent distinct source records, and their scope is limited to their respective check dates. The HTTP 403 status only describes the response recorded on 2026-10-01 and does not indicate content or availability at other times. The sequence of dated checks allows for comparison but does not imply any trend or change between observations.
Recommended Actions
For feat-edit-competition.dydx-trading-competition-frontend-production.pages.dev, retain the records from MetaMask, SEAL, and VirusTotal for future reference and comparison. Keep the HTTP response and PageSpeed performance records as separate observations. When reviewing the domain, compare each source individually and schedule new checks to update the evidence set.
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-26 10:28:17 UTCcurrent episode first observed: 2026-10-01 01:35:41 UTCobserved RIP window: 2026-08-26 10:28:17 UTC → 2026-10-01 01:35:41 UTC · 855.12hmidpoint estimate ≈ 2026-09-13 06:01:59 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.
技术 · 3 identified
H
HSTS
安全
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
ADMINUSLabs
ChainPatrol
alphaMountain.ai
BitDefender
CyRadar
ESET
Fortinet
G-Data
卡巴斯基
Lionic
Sophos
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of feat-edit-competition.dydx-trading-competition-frontend-production.pages.dev· checked Sep 1, 2026
99
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.85s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.11s
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-01 01:00:23 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-08-31 23:53:11 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
7 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)
