The domain babybeehq.shop was observed on 2026-10-09, with its inclusion in the PhishDestroy internal catalogue recorded on that date. VirusTotal also provided a scan result for this domain on 2026-10-09, offering additional insight into its status at that time.
Recorded Evidence
On 2026-10-09, the PhishDestroy internal catalogue listed babybeehq.shop. VirusTotal recorded 1 detection out of 92 scanners for this domain on the same date. OTX referenced babybeehq.shop in 2 pulses as of 2026-10-09. The domain was registered with Dynadot Inc. on 2026-05-16.
Interpretation
The records from PhishDestroy, VirusTotal, and OTX each provide distinct observations about babybeehq.shop on 2026-10-09. These sources collectively offer a view into the domain's status and references across multiple platforms, which can be useful for tracking its presence and any changes over time.
Recommended Actions
Preserve the PhishDestroy internal listing and the VirusTotal detection record for babybeehq.shop as reference points. Compare these with the OTX pulse references in future reviews to monitor for any new developments or additional observations.
スキャナーに関する注記:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='babybeehq.shop', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError
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-11 10:04:24 UTC
RDAP registration不明
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.
Last analyzed Previous stored snapshot: 1 detection
alphaMountain.ai
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-09 01:25:56 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 146.19.203.200.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 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.
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)
