On 2026-10-01, bridge-kind-52.pages.dev responded with HTTP status 403 according to a recorded HTTP check. The domain is also included in a PhishDestroy internal listing, which is a catalogue entry maintained by the publisher.
Recorded Evidence
The domain was first observed on 2026-09-13. A VirusTotal scan on 2026-09-19 found 1 detection out of 89 scanners, with the observation time marked as unknown. An SSL scan on the same date identified the certificate issuer as Google Trust Services / WE1. The PhishDestroy internal listing is also recorded for this domain.
Interpretation
The HTTP 403 status reflects only the response to a specific request on 2026-10-01 and does not describe all possible content served by bridge-kind-52.pages.dev. The VirusTotal detection and the PhishDestroy internal listing are separate source observations, each using different methods to record their findings. The SSL certificate and first observation dates provide additional context for the domain's technical configuration and monitoring timeline.
Recommended Actions
For bridge-kind-52.pages.dev, retain the PhishDestroy listing and VirusTotal scan as distinct records for future reference. Compare the HTTP status check with the initial observation date to track any changes in recorded responses. Keep the SSL scan result available for technical reviews alongside the other dated evidence.
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:07 UTCcurrent episode first observed: 2026-10-01 01:53:14 UTCobserved RIP window: 2026-09-13 14:28:07 UTC → 2026-10-01 01:53:14 UTC · 419.42hmidpoint estimate ≈ 2026-09-22 08:10:40 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:27 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-19 18:23:49 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
6 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)
