balibodystore.shop returned an HTTP status 200 on 2026-10-11, documenting a successful response at that time. The domain was also listed in the PhishDestroy internal catalogue as of the same period.
Recorded Evidence
The HTTP status source recorded a 200 code for balibodystore.shop on 2026-10-11. PhishDestroy included the domain in its internal listing as of 2026-10-11. OTX referenced four pulses for this domain on 2026-10-11. The registrar was Dynadot Inc., with registration dated 2026-05-21, and the SSL certificate was issued by Let's Encrypt / YE2 as of 2026-10-10.
Interpretation
PhishDestroy’s listing is a record of internal catalogue inclusion, while the HTTP status source documents a specific response code returned by the domain. OTX pulses represent external intelligence entries referencing the domain, each potentially reflecting distinct observations or community reports. These sources together provide a snapshot of technical and reputational data for balibodystore.shop as of their respective dates.
Recommended Actions
For balibodystore.shop, retain the HTTP status 200 record and PhishDestroy internal listing for future comparison. Review the OTX pulse references to track any changes in external intelligence over time. Preserve all dated evidence to monitor developments and inform subsequent assessments of the domain.
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:00:23 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:23 UTClast content: 2026-10-11 10:00:23 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:02:46 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.200.
脅威対応 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.
(US)
