On 2026-10-01, projectsdapps.pages.dev returned an HTTP 403 status code according to a recorded HTTP check. The same source set records a first observation date of 2026-09-13 for this domain. A PhishDestroy internal listing is also recorded, and VirusTotal reported 0 detections across 89 scanners on 2026-09-19.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 403, while the SSL scan dated 2026-09-19 named Google Trust Services / WE1 as issuer. VirusTotal, checked on 2026-09-19, recorded 0 detections out of 89 scanners. The PhishDestroy internal listing and the first observation dated 2026-09-13 complete the recorded set.
Interpretation
The dated HTTP response describes only the reply recorded at that check, not the domain's content or present availability. The PhishDestroy catalogue entry and the VirusTotal result are separate source observations, and their differing dates and metrics do not establish a trend. The first observation date marks when the domain entered these records, not when it was created.
Recommended Actions
Preserve the HTTP check, the VirusTotal result, the PhishDestroy internal listing, and the first observation record for projectsdapps.pages.dev. Compare the HTTP record and the VirusTotal record separately in later reviews, since each measures a different thing. Avoid submitting credentials or personal information to projectsdapps.pages.dev while these records remain the basis for review.
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-09-13 14:28:08 UTCcurrent episode first observed: 2026-10-01 01:53:14 UTCobserved RIP window: 2026-09-13 14:28:08 UTC → 2026-10-01 01:53:14 UTC · 419.42hmidpoint estimate ≈ 2026-09-22 08:10:41 UTC · precision 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.
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-19 22:00:26 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-19 18:23:50 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.
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)
