applecrumbybaby.shop appears in the PhishDestroy internal listing, a record dated 2026-10-02, and the same date carries an OTX pulse count of 1. A separate scanner check on 2026-10-02 returned 11 detections across 91 scanners, while a PageSpeed performance score of 56 was also logged that day.
Recorded Evidence
The PhishDestroy internal listing for applecrumbybaby.shop was recorded on 2026-10-02. VirusTotal reported 11 detections out of 91 total scanners on 2026-10-02. OTX recorded 1 pulse on 2026-10-02. The PageSpeed performance score was 56 on 2026-10-02. The first observation date for the domain was 2026-10-02, and the resolved IP address was 195.96.130.231.
Interpretation
The PhishDestroy catalogue entry and the OTX pulse are separate named source records that each describe the domain on the same calendar date. The VirusTotal detection ratio and the PageSpeed score measure different things, so they should be read as distinct observations rather than combined into a single judgment. Because all recorded dates fall on one day, the evidence does not show a sequence or change over time.
Recommended Actions
Preserve the PhishDestroy listing record and the OTX pulse record for applecrumbybaby.shop as separate items, since each names a distinct source. Compare the VirusTotal detection record against the OTX record when reviewing the domain, and keep the PageSpeed record alongside them for context. Recheck each named source before relying on any single entry about applecrumbybaby.shop.
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:08:45 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:08:45 UTClast content: 2026-10-11 10:08:45 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.
Google PageSpeed Insights — mobile performance audit of applecrumbybaby.shop· checked Oct 2, 2026
56
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
8.93s
Largest Contentful Paint
CLS
0.021
Cumulative Layout Shift
TBT
456ms
Total Blocking Time
SI
3.92s
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-02 19:21:23 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.231.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
11 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.
