babybrezza.shop was observed on 2026-10-09 with two OTX pulses and a PhishDestroy internal listing. The domain spelling does not indicate any specific product or brand beyond the recorded label.
Recorded Evidence
babybrezza.shop was first observed on 2026-10-09 with an IP address of 146.19.203.205. OTX recorded two pulses on 2026-10-09. VirusTotal checked the domain on 2026-09-20 with 0 detections out of 92 scanners. PhishDestroy listed the domain internally on 2026-10-09.
Interpretation
The observations span two dates: VirusTotal’s scan on 2026-09-20 and OTX plus PhishDestroy records on 2026-10-09. Each source provides a dated snapshot of the domain’s status without implying ongoing conditions. The chronology shows VirusTotal’s earlier check followed by same-day OTX and PhishDestroy listings.
Recommended Actions
For babybrezza.shop, preserve the VirusTotal scan record from 2026-09-20 and the OTX pulses and PhishDestroy listing from 2026-10-09. Compare these dated records when reviewing the domain’s status over time.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 10:04:34 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.
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:29:17 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 146.19.203.205.
위협 대응 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
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026년 10월 9일
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)
