On 2026-10-10, bambaswimstore.shop was recorded with a PhishDestroy internal listing, which is a publisher-owned catalogue entry. The domain was also observed with an SSL certificate issued by Let's Encrypt / YE1, providing additional technical context for its infrastructure.
Recorded Evidence
PhishDestroy internally listed bambaswimstore.shop on 2026-10-10. The SSL certificate for the domain was issued by Let's Encrypt / YE1 and was scanned on 2026-10-10. The domain was first observed on 2026-10-10, and the associated network organization at that time was AS199242 Malakmadze Web LLC, with an IP address located in the US.
Interpretation
The PhishDestroy record contains a listing that documents the domain's inclusion in a publisher-owned catalogue. This type of measurement provides a record of the domain as seen by the source on a specific date, which can be useful for tracking changes or comparisons over time. The evidence covers technical aspects and network associations, offering a snapshot of the domain's infrastructure and listing status as of the recorded date.
Recommended Actions
For bambaswimstore.shop, preserve the PhishDestroy internal listing and SSL certificate scan records for future reference. Compare these source records with any subsequent observations to identify changes in listing status or technical configuration. Use the documented evidence to inform any further review or monitoring of the domain's recorded history.
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:00:24 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:24 UTClast content: 2026-10-11 10:00:24 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.
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-10 17:11:13 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.219.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
