VirusTotal
17 / 92 engine detections
レポートを開く“Adenofrin | AI Trading Platform | Official Website”
フィッシング: adenofrin.click — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 17/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, DNS8); URLScan capture; CF Radar…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 92 engine detections
レポートを開く悪意あり
レポートを開くScan report
レポートを開く1 community reference
レポートを開くNo threat flag
レポートを開くPage capture
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has listed adenofrin.click as a suspicious domain. No page title or content was recorded at the time of analysis. The domain first appeared in PhishDestroy’s monitoring on 2026-10-20.
The current classification does not point to a particular fraud technique. Domains that receive multiple vendor detections are often used for phishing, credential harvesting, or malware distribution, but no concrete activity has been observed on this site. Consequently, the listing reflects risk based on external signals rather than verified malicious actions.
VirusTotal reported 17 detections from 92 scanning engines, with vendors such as AlphaMountain.ai, BitDefender, CRDF, CyRadar, DNS8, ESET, Forcepoint ThreatSeeker and Fortinet flagging the domain; the results were retrieved on 2026-10-20 and the scan was performed on 2026-10-18. Google Safe Browsing checked the URL on 2026-10-20 and did not flag it. PhishDestroy’s internal blocklist includes the domain as of 2026-10-20, while external blocklists reported zero hits on the same date. OTX listed one pulse referencing adenofrin.click on 2026-10-20.
The domain was registered on 2026-05-19 through Dynadot, LLC. Network records show the site resolving to IP address 185.62.56.121 at the time of observation.
Visitors should avoid entering any credentials or personal information on adenofrin.click. If credentials were submitted, change the associated passwords and enable multi‑factor authentication where possible. Defenders can add a rule to block or monitor traffic to adenofrin.click and review server logs for any connections to 185.62.56.121.
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.
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.
brian.ns.cloudflare.comsandra.ns.cloudflare.comLocation describes the IP network.
93a9c8ce89cc184a03d97943bd280b24f7c62fa2eb8f0b4f1942c7d7851b79b0Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of adenofrin.click · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://adenofrin.click/https://adenofrin.click/Content-Encoding: gzipContent-Type: text/html; charset=utf-8h3=":443"; ma=2592000gziptext/html; charset=utf-8Tue, 20 Oct 2026 09:53:18 GMT"dm9jrjkbl0kp12u5-gzip"Tue, 20 Oct 2026 09:10:34 GMTno-referrer-when-downgradechunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能
PD-20261020-2069E2
1 community references
View sourceNo threat flag
View source17/92 engine detections
View sourceadenofrin.click
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
adenofrin.click
PD-20261020-2069E2 Recipient: abuse@dynadot.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
adenofrin.click)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.