bataglobal.shop was recorded in a PhishDestroy internal listing on 2026-10-12, providing a dated entry for its presence in this publisher-owned catalogue. The domain was first observed in technical records on 2026-10-11, establishing a timeline for its initial appearance.
Recorded Evidence
PhishDestroy internally listed bataglobal.shop on 2026-10-12. VirusTotal checked the domain on 2026-10-11, recording 16 detections out of 92 total scanners. OTX documented two pulses referencing bataglobal.shop as of 2026-10-12. The domain’s first observation was on 2026-10-11.
Interpretation
PhishDestroy provides an internal listing of bataglobal.shop, documenting its inclusion in a publisher-owned catalogue. VirusTotal contains a technical measurement, detailing how the domain was assessed by multiple security scanners. OTX records show that the domain was referenced in two intelligence pulses, broadening the scope of recorded observations.
Recommended Actions
For bataglobal.shop, preserve the PhishDestroy internal listing and VirusTotal scan records for ongoing reference. Review OTX pulse entries to compare changes in intelligence context. Maintain these source records to support future technical or investigative steps involving 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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:36:52 UTC
RDAP registration未知
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-12 11:05:15 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.244.119.42.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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)
