bridgeengine.online was recorded in the PhishDestroy internal listing on 2026-10-13, establishing a dated entry in a publisher-owned catalogue. On the same date, a PageSpeed performance score of 74 was documented for the domain, providing a technical measurement of its web performance.
Recorded Evidence
VirusTotal checked bridgeengine.online on 2026-10-13, recording 0 detections out of 92 total scanners. The PhishDestroy internal listing included the domain as of 2026-10-13. OTX referenced bridgeengine.online in four pulses on 2026-10-13. The domain was registered through Global Domain Group LLC on 2026-09-30, and its PageSpeed performance score was 74 on 2026-10-13.
Interpretation
The PhishDestroy internal listing contains a record of bridgeengine.online, which documents its inclusion in a publisher-managed catalogue. VirusTotal provides a measurement of detection results from a range of security vendors, while OTX records offer additional context through pulse references. These sources together capture a technical and chronological overview of the domain's recorded status as of their respective dates.
Recommended Actions
For bridgeengine.online, retain the VirusTotal, PhishDestroy, and OTX records for ongoing comparison and reference. Review the PageSpeed performance score as a technical benchmark in future assessments. Use these dated records as a basis for tracking changes in the domain's recorded indicators.
登録情報作成日 2026年9月30日 (13d · Very New!)—Expires 2027年9月30日
技術詳細Provenance & timestamps
初確認2026年10月13日
Submitted URLhttps://bridgeengine.online/
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Probe Inconclusive20%2026-10-13 11:42:26 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 11:42:26 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.
Values retained by the collector; long values may be shortened during collection.
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-10-13 11:42:26 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.24.57.1.
脅威対応 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.
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.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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)
