batikapparel.shop was observed with an HTTP status code of 200 on 2026-10-11, confirming a successful response on that date. The domain also had a PhishDestroy internal listing recorded, which is a notable entry in the publisher's own catalogue.
Recorded Evidence
On 2026-10-11, the HTTP status for batikapparel.shop was recorded as 200, documenting a successful web response. The same day, OTX recorded four pulses for the domain. PhishDestroy listed the domain internally as of 2026-10-11. Additionally, a URLScan report was available for review on 2026-10-11.
Interpretation
The PhishDestroy listing contains a publisher-specific record documenting batikapparel.shop. OTX provides pulse counts, which are a type of security intelligence signal related to the domain. The HTTP status record measures the web server's response at a specific point in time. These sources together provide a multi-faceted technical profile of the domain's observed state on the recorded date.
Recommended Actions
Preserve the HTTP status, PhishDestroy listing, OTX pulse count, and URLScan report records for batikapparel.shop for future reference. Compare these source records when reviewing subsequent observations or conducting further technical assessments of the 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:00:33 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:33 UTClast content: 2026-10-11 10:00:33 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 00:16:56 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.198.
脅威対応 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.
