babyletto.shop was observed in a VirusTotal scan on 2026-10-04, which recorded both detections and total scanners. The domain was also listed in the PhishDestroy internal catalogue as of 2026-10-09.
Recorded Evidence
VirusTotal reported 5 detections out of 92 total scanners for babyletto.shop on 2026-10-04. OTX included this domain in 4 pulses as of 2026-10-09. The domain appeared in the PhishDestroy internal listing on 2026-10-09. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-09. The PageSpeed performance score was 83 as of 2026-10-09.
Interpretation
These source records provide a snapshot of babyletto.shop's presence in multiple security and performance monitoring systems. The VirusTotal and OTX observations indicate that this domain was actively monitored and flagged by several sources. The PhishDestroy internal listing further documents its inclusion in a publisher-maintained catalogue. SSL and PageSpeed data add context to the domain's technical configuration and performance at the time of observation.
Recommended Actions
Review the VirusTotal and OTX records for babyletto.shop to understand the security context provided by these sources. Preserve the PhishDestroy internal listing and PageSpeed performance score for future comparison. Use these dated records as a baseline for ongoing monitoring and evaluation of this domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:40:52 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:40:52 UTClast content: 2026-10-11 10:40:52 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.
使用技術 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
G-Data
Gridinsoft
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of babyletto.shop· checked Oct 9, 2026
83
Needs Work
Performance
FCP
3.45s
First Contentful Paint
LCP
3.45s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
68ms
Total Blocking Time
SI
3.45s
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-09 02:37:25 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.211.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
10 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.
