The domain aawe.finance was registered on October 09, 2025 through Tucows Domains Inc. and resolves to the IP address 172.67.188.157, which is owned by AS13335 Cloudflare, Inc. and geolocated to the United States. The site is currently taken offline, but historical evidence indicates it was used as a crypto drainer employing the Angel Drainer kit and is classified as a wallet/seed phishing operation targeting the BNB chain. The page title returned from the host reads "Exchange | PancakeSwap," suggesting an attempt to masquerade as the legitimate PancakeSwap exchange. No SSL certificate is presented, leaving any communication unencrypted and exposing users to credential capture.
Infrastructure analysis shows three distinct nameservers (1-ceci.njalla.do, 2-nest.pipe.ma, 3-pas.njalla.in), a pattern often associated with fast‑flux or disposable hosting used by malicious actors. VirusTotal scans have flagged the domain in 14 out of 95 security vendor engines, and it appears on at least one public security blocklist. Additionally, PhishDestroy has listed the domain as blocked, reinforcing the assessment of malicious intent.
While the domain is offline, the combination of a high‑risk classification, confirmed use of a known drainer kit, impersonation of a reputable blockchain brand, and multiple detection sources provides strong evidence of a credential‑stealing operation. Defenders should immediately block aawe.finance at DNS and proxy layers, monitor for any resurrection of the domain or related sub‑domains, and enforce strict verification of BNB‑chain related URLs within their environments. Users should be warned that any unsolicited requests for wallet seeds or private keys associated with this domain are fraudulent, and any credentials previously entered should be considered compromised and rotated without delay.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='aawe.finance', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
DOM Analysisanalyzed 2026年3月24日score 15/1002 brand signals
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:14:44 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:17:47 UTCcurrent episode first observed: 2026-10-10 20:20:48 UTCobserved RIP window: 2026-09-15 22:17:47 UTC → 2026-10-10 20:20:48 UTC · 598.05hmidpoint estimate ≈ 2026-09-28 09:19:17 UTC · precision low · basis bounded
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.
Last analyzed Previous stored snapshot: 15 detections
ADMINUSLabs
alphaMountain.ai
AlphaSOC
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
カスペルスキー
Lionic
SOCRadar
ソフォス
VIPRE
Webroot
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
あなたの仮想通貨取引所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
(CA)
