batteriesamerica.shop returned an HTTP status 200 on 2026-10-11, documenting a successful response to a request on that date. The domain was also observed as listed in the PhishDestroy internal catalogue.
Recorded Evidence
On 2026-10-11, the HTTP status source recorded a 200 response code for batteriesamerica.shop. The same day, PhishDestroy internally listed the domain, and OTX recorded four pulses referencing it. URLScan produced a report for the domain on 2026-10-11. The domain was registered with Dynadot Inc. on 2026-05-04, and its SSL certificate was issued by Let's Encrypt / YE1.
Interpretation
The PhishDestroy source contains a record of batteriesamerica.shop in its internal listing, which is a catalogue of domains of interest. OTX provides a measurement of community-contributed pulses referencing the domain, documenting external attention. The HTTP status record describes a successful response on the observed date, while URLScan's report offers a technical snapshot of the domain's web presence. These sources collectively cover technical response, catalogue inclusion, and external intelligence references, offering a range of perspectives on the domain's recorded profile.
Recommended Actions
For batteriesamerica.shop, retain the HTTP status record and the URLScan report for future technical comparisons. Preserve the PhishDestroy internal listing and OTX pulse records to monitor for changes in catalogue status and external intelligence references. Review these sources periodically to assess any updates or new observations relevant to the domain.
DOM Analysisanalyzed 2026年10月11日score 78/1001 brand signal
Submitted URLhttp://batteriesamerica.shop/
Favicon Hash
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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:32 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:00:32 UTClast content: 2026-10-11 10:00:32 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:19:14 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 212.52.28.51.
威胁响应 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)
