On 2026-10-10, batterytenderhq.shop was observed as a listing in the phishdestroy internal database, according to a recorded source observation. The domain also has a recorded SSL certificate scan from the same day, which contributes to its technical profile.
Recorded Evidence
A PhishDestroy internal listing for batterytenderhq.shop was recorded on 2026-10-11. The domain was registered with Dynadot Inc. on 2026-05-21. An SSL certificate issued by Let's Encrypt / YE2 was scanned on 2026-10-11, documenting the domain’s encryption status at that time.
Interpretation
The PhishDestroy source contains a listing entry for batterytenderhq.shop, which records its presence in a publisher-managed catalogue. This type of measurement documents the domain’s inclusion in a specific internal reference. The SSL scan and registration records provide additional context for the domain’s infrastructure as of their respective dates.
Recommended Actions
For batterytenderhq.shop, retain the PhishDestroy catalogue listing and related technical records for future reference. Compare these source records in subsequent reviews to identify any new or changed observations. Use the documented evidence to inform ongoing monitoring and analysis 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:34 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:34 UTClast content: 2026-10-11 10:00:34 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:32:34 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.237.
脅威対応 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)
