The domain bozel.net was observed in a MetaMask blocklist entry on 2026-10-13, which is a recorded external source. Additionally, a low PageSpeed performance score was documented for this domain, providing further technical context.
Recorded Evidence
On 2026-10-13, bozel.net appeared on both the MetaMask and SEAL external blocklists. OTX recorded two pulses for this domain on the same date. VirusTotal checked bozel.net on 2026-10-08 and reported 0 detections out of 92 scanners. The domain was listed internally by PhishDestroy as of 2026-10-13. The registrar was recorded as Gname.com Pte. Ltd. with a registration date of 2026-10-07. The PageSpeed performance score was 33, as checked on 2026-10-13.
Interpretation
The PhishDestroy internal listing provides a record of bozel.net's inclusion in a security-focused database, which documents domains of interest for monitoring. VirusTotal's measurement offers a snapshot of how many security scanners detected issues with the domain at a specific time. These records, along with the external blocklist entries, form a technical profile of the domain's presence in various security intelligence sources.
Recommended Actions
For bozel.net, retain the MetaMask and SEAL blocklist records as references for future security reviews. Preserve the VirusTotal and OTX records to compare with subsequent scans and intelligence updates. Monitoring these sources over time will help track changes in the domain's recorded status and inform any necessary actions based on updated evidence.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Google PageSpeed Insights — mobile performance audit of bozel.net· checked Oct 13, 2026
33
Poor
Performance
FCP
7.55s
First Contentful Paint
LCP
13.59s
Largest Contentful Paint
CLS
0.976
Cumulative Layout Shift
TBT
17ms
Total Blocking Time
SI
7.55s
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.
Threat First Observed2026-10-12 23:43:08 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.176.27.
Threat Response Pipeline
Discovery
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.
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 13, 2026
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 13, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
3 evidence signal groups linked0 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
(SG)
