The domain baobabcollectionstudio.shop returned an HTTP status 200 on 2026-10-11, showing that a server response was recorded on that date. The domain was also present in the PhishDestroy internal listing as of the same day, providing an additional reference point for its observation.
Recorded Evidence
On 2026-10-11, baobabcollectionstudio.shop was observed with an HTTP status 200, documenting a successful server response. The PhishDestroy internal listing included this domain on 2026-10-11. The SSL certificate for the domain was issued by Let's Encrypt / YE1 and was scanned on 2026-10-11. The first observation of this domain was also recorded on 2026-10-11.
Interpretation
The HTTP status source records the specific server response code, which in this instance was 200, documenting that a response was received from the domain. The PhishDestroy source contains a listing entry for baobabcollectionstudio.shop, serving as an internal catalogue reference. Together with the SSL certificate scan, these sources provide a technical snapshot of the domain's observed state on the recorded dates.
Recommended Actions
For baobabcollectionstudio.shop, retain the HTTP status and PhishDestroy internal listing records for ongoing monitoring and future comparison. Compare these source records periodically to track any changes in server response or catalogue status. The SSL certificate scan should also be preserved for reference in future security reviews.
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:43:14 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:43:14 UTClast content: 2026-10-11 10:43:14 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 22:44:23 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.232.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
10 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.
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
