ballislifestore.shop was recorded in the PhishDestroy internal listing on 2026-10-10, providing a dated reference for its presence in a security catalogue. The domain was also observed with a valid SSL certificate issued by Let's Encrypt on the same date.
Recorded Evidence
The PhishDestroy internal listing documents ballislifestore.shop as present in its catalogue on 2026-10-10. The SSL certificate for the domain was issued by Let's Encrypt / YE1 and was scanned on 2026-10-10. The domain was first observed on 2026-10-10, and its network infrastructure was associated with AS199242 Malakmadze Web LLC in the US at that time.
Interpretation
PhishDestroy contains a record for ballislifestore.shop, which catalogs the domain as part of its internal security listings. This record provides a reference point for security analysis, documenting the domain's presence in a monitored environment. The available evidence also includes technical details such as SSL certificate issuance and network organization, offering a broader context for infrastructure review.
Recommended Actions
For ballislifestore.shop, retain the PhishDestroy internal listing as a reference for future security comparisons. Compare the domain's presence in additional security sources if they become available. Review the technical evidence for consistency with other observed domains in the same network environment.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
DOM Analysisanalyzed 2026년 10월 10일score 63/1002 brand signals
Submitted URLhttp://ballislifestore.shop/
Favicon Hash
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:24 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:00:24 UTClast content: 2026-10-11 10:00:24 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:06:50 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.236.
위협 대응 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(US)
