briidge-base.pages.dev returned HTTP status 403 in a check recorded on 2026-10-01, the most recent HTTP observation in this evidence set. The same record set includes a Google Safe Browsing flag for social engineering dated 2026-09-16.
Recorded Evidence
Google Safe Browsing flagged the domain on 2026-09-16 with a social engineering threat. VirusTotal recorded 8 detections across 89 scanners on 2026-09-16. The domain appeared on the MetaMask and SEAL external blocklists as of 2026-10-02. PhishDestroy's internal listing was recorded, and the domain was first observed on 2026-09-03.
Interpretation
The Safe Browsing flag, VirusTotal detections and blocklist entries are separate source records that describe different checks rather than one combined measurement. The first-observed date and the later checks show a sequence, but the exact dates do not establish when any listing began or whether conditions changed. The 403 response describes only the recorded HTTP reply, not all content that may exist on the domain.
Recommended Actions
Preserve the Safe Browsing, VirusTotal, MetaMask, SEAL and PhishDestroy records for briidge-base.pages.dev. Compare those source records against later checks of briidge-base.pages.dev. Treat the recorded HTTP response as a single dated observation rather than a current status.
Observed timelinelast reachable: 2026-09-03 14:28:08 UTCcurrent episode first observed: 2026-10-01 01:39:23 UTCobserved RIP window: 2026-09-03 14:28:08 UTC → 2026-10-01 01:39:23 UTC · 659.19hmidpoint estimate ≈ 2026-09-17 08:03:45 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.
技术 · 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: 8 detections
alphaMountain.ai
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Sophos
VIPRE
网站性能分析
Google PageSpeed Insights — mobile performance audit of briidge-base.pages.dev· checked Sep 14, 2026
99
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.83s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.17s
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.
VirusTotal Detections Update2026-09-14 17:50:43 UTC
VirusTotal scanner detections updated from 4 to 8. Added scanner alerts: ESET, Fortinet, G-Data, Sophos.
Domain Status Transition2026-09-14 10:00:19 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-14 07:40:03 UTC
Telemetry event observed.
Threat First Observed2026-09-14 07:33:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
已捕获威胁
briidge-base.pages.dev 已检测到并排入队，待进行全面分析
2026年9月3日
Cloudflare Radar Report
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)
