distributions-aave.icu was first observed in a PhishDestroy internal listing on 2026-10-11, which documents its presence in a security intelligence context. The domain also appeared on three external blocklists on the same date, providing further recorded indicators.
Recorded Evidence
PhishDestroy internally listed distributions-aave.icu on 2026-10-11. On that date, MetaMask, ScamSniffer, and SEAL each included the domain in their external blocklists. The domain's registration was recorded with Eranet International Limited on 2026-10-01, and an SSL certificate issued by Let's Encrypt / YE1 was scanned on 2026-10-11.
Interpretation
PhishDestroy provides a dated internal listing of distributions-aave.icu, capturing its inclusion in a monitored environment. The MetaMask, ScamSniffer, and SEAL blocklists record external detections, each documenting the domain's status as observed by their respective systems. These sources together offer a snapshot of the domain's recorded security context shortly after its registration.
Recommended Actions
For distributions-aave.icu, preserve the PhishDestroy internal listing and the blocklist entries from MetaMask, ScamSniffer, and SEAL for ongoing comparison. Reference these records when reviewing new blocklist entries or updated intelligence to track changes in the domain's recorded status.
登録情報作成日 2026年10月1日 (9d · Very New!)—Expires 2027年10月1日
技術詳細Provenance & timestamps
初確認2026年10月11日
DOM Analysisanalyzed 2026年10月11日score 85/1004 brand signals
Submitted URLhttp://distributions-aave.icu/
Favicon Hash
ケース ID
SHORTDOTゾーン · 公開証拠.icu
ShortDot zone evidence
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 12:30:35 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 12:30:35 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 12:30:35 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.4.7.
脅威対応 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.
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)
