batterytenderauto.shop was observed with an HTTP status 200 response on 2026-10-11, documenting a successful connection on that date. The domain also appears in a publisher-owned PhishDestroy internal listing as of the same day.
Recorded Evidence
The HTTP status record from 2026-10-11 shows a 200 code, confirming a valid response. OTX contains four pulse entries for batterytenderauto.shop, all checked on 2026-10-11. The domain was registered with Dynadot Inc. on 2026-05-18, and its SSL certificate was issued by Let's Encrypt / YE1, with scanning also recorded on 2026-10-11. URLScan reported a capture of the domain on 2026-10-11, and the PhishDestroy internal listing was documented on the same date.
Interpretation
The OTX source documents four pulse entries, which are measurements of external intelligence activity related to batterytenderauto.shop. The HTTP status record provides a technical observation of the domain’s response capability, while PhishDestroy catalogs the domain in its internal listing. These records capture a range of technical and intelligence observations, offering a snapshot of the domain’s profile as of 2026-10-11.
Recommended Actions
For batterytenderauto.shop, preserve the HTTP status and OTX records for future comparison and reference. Retain the PhishDestroy internal listing and URLScan capture as part of ongoing monitoring. Review these dated evidence sources regularly to track any changes in the domain’s recorded profile.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
DOM Analysisanalyzed 2026년 10월 11일score 71/1001 brand signal
Submitted URLhttp://batterytenderauto.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: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:35 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.245.239.168.
위협 대응 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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.
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(US)
