The domain bose.locker was registered on July 19, 2026 through Gname.com Pte. Ltd. and is currently active. Its authoritative name servers are crystal.ns.cloudflare.com and leo.ns.cloudflare.com, both operated by Cloudflare. DNS resolution points to the single IPv4 address 188.114.97.3. The domain appears on one public security blocklist and is explicitly blocked by the PhishDestroy feed, indicating that threat‑intelligence sources have already identified it as malicious.
VirusTotal records show that the domain was scanned by 91 anti‑malware vendors; at the time of analysis none of those vendors reported a detection. While the lack of detections does not constitute a safety guarantee, it confirms that the sample has been examined by a broad set of scanners. No additional public reputation services, such as Safe Browsing or OTX, are referenced in the available data, and no SSL certificate details or HTTP response codes have been disclosed. Consequently, the technical picture is limited to registration metadata, hosting infrastructure, and blocklist presence.
The primary uncertainty lies in the specific payload or credential‑harvesting mechanisms hosted at the domain, as no page title, brand targeting, or kit information has been reported. Defenders should treat bose.locker as a high‑confidence phishing indicator: block the domain at network perimeters, update DNS filtering policies, and monitor for any outbound connections to 188.114.97.3. Continuous re‑scanning with sandbox and URL‑analysis tools is advised to capture any evolving malicious content. Organizations that have observed related phishing attempts should correlate timestamps with the July 19 creation date to assess potential exposure.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bose.locker', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
DOM Analysisanalyzed 2026年7月23日score 95/1001 brand signal
Submitted URLhttp://bose.locker/
Favicon Hash
ケース ID
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-13 01:12:36 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-07-30 22:22:05 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-30 22:22:05 UTC → 2026-09-30 16:14:55 UTC · 1,481.88hmidpoint estimate ≈ 2026-08-30 19:18:30 UTC · precision very 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.
使用技術 · 5 identified
V
Vue.js
JavaScript frameworks
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of bose.locker· checked Jul 23, 2026
34
Poor
Performance
FCP
7.26s
First Contentful Paint
LCP
12.98s
Largest Contentful Paint
CLS
0.657
Cumulative Layout Shift
TBT
37ms
Total Blocking Time
SI
8.57s
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.
Domain Status Transition2026-08-05 22:02:27 UTC
Domain state transitioned from alive to dead.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
14 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
(HK)
