The domain baysebrand.shop returned an HTTP status 200 on 2026-10-11, documenting a successful response at that time. On the same date, a listing in the PhishDestroy internal catalogue was recorded for this domain.
Recorded Evidence
PhishDestroy internally listed baysebrand.shop on 2026-10-11. The HTTP status source recorded a 200 response code on 2026-10-11. OTX referenced this domain in four pulses as of 2026-10-11. URLScan had a report available for this domain on 2026-10-11. The domain was registered with Dynadot Inc. on 2026-04-17, and the SSL certificate was issued by Let's Encrypt / YE2.
Interpretation
The PhishDestroy record contains an internal listing, which is a catalogue entry maintained by the publisher. The HTTP status source documents a successful connection to the domain on a specific date, providing a technical observation of its response. OTX records reference this domain in multiple pulses, which are collections of related security intelligence. These sources together provide a snapshot of the domain's presence in various security and technical monitoring platforms as of the recorded dates.
Recommended Actions
For baysebrand.shop, preserve the PhishDestroy internal listing and the HTTP status 200 record for future comparison. Retain the OTX pulse references and the URLScan report as part of ongoing monitoring. Comparing these source records over time may help track changes in the domain's technical and security-related observations.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:23:03 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 01:23:03 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-11 01:23:03 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 162.222.90.17.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
9 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.
(US)
