balaboostejewelry.shop was first observed on 2026-10-10, with a PhishDestroy internal listing documented on the same date. The domain’s registration with Dynadot Inc. was recorded earlier, providing a timeline for its presence in available records.
Recorded Evidence
PhishDestroy internally listed balaboostejewelry.shop on 2026-10-10. The domain’s registration date with Dynadot Inc. is recorded as 2026-05-17. Its network infrastructure was documented with an IP address in the US, associated with AS199242 Malakmadze Web LLC, as observed on 2026-10-10.
Interpretation
The PhishDestroy source contains a listing for balaboostejewelry.shop, documenting its inclusion in the publisher’s internal catalogue. This measurement provides a dated reference for the domain’s presence in a security-related listing. The timeline established by the registration and observation dates allows for comparison of its recorded history and infrastructure.
Recommended Actions
For balaboostejewelry.shop, preserve the PhishDestroy internal listing and registration records for future reference. Compare these source records periodically to monitor any new observations or changes related to the domain’s documented evidence.
DOM Analysisanalyzed 2026年10月10日score 73/1001 brand signal
Submitted URLhttp://balaboostejewelry.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:22 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:22 UTClast content: 2026-10-11 10:00:22 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 16:57:54 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.135.
脅威対応 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)
