VirusTotal
12 / 89 engine detections
レポートを開く“TronSwap â Fastest Token Swap & DEX Aggregator on TRON Network”
Security analysis of www.tronswap.net covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 89 engine detections
レポートを開く1 threat-system alert
レポートを開くDBL_PHISH
no community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | www.tronswap.net |
malicious | Sinkholed |
PhishDestroy threat report
The domain www.tronswap.net was registered on July 29, 2026 by Fewmoretaps OU doing business as Trustname.com and is served by the authoritative name servers ares.trustname.com and zeus.trustname.com. DNS resolution points to the single IPv4 address 186.2.175.35. The domain appears on one public security blocklist and has been specifically flagged by the PhishDestroy blocklist, indicating that at least one external mitigation service has identified it as a phishing vector. A VirusTotal scan was performed by 91 independent scanning engines; none of the engines reported a detection at the time of analysis.
While the absence of detections does not constitute proof of legitimacy, it does demonstrate that the payload observed by the scanners did not match known malicious signatures. No additional intelligence such as Safe Browsing verdicts, Open Threat Exchange entries, SSL certificate details, HTTP response codes, or page title metadata is currently available. Consequently, the precise content and the exact phishing technique employed remain unknown.
Defenders should treat the domain as hostile until further evidence is obtained. Recommended actions include adding 186.2.175.35 to network‑level deny lists, enforcing DNS sinkholing for www.tronswap.net, monitoring outbound connections to the associated name servers, and employing URL filtering that references the PhishDestroy blocklist. Continuous re‑scanning of the domain with dynamic analysis tools is advised to capture any payload changes, and any observed credential harvesting attempts should be logged and investigated.
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.
ares.trustname.comzeus.trustname.comLocation describes the IP network.
ff0a689507b3adde9ab9d306d6e8864507835b47948460702c7c8a27c25de45aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
到達可能→利用不可
12/89 engine detections
View sourceNo threat flag
View sourcePage captured
View sourceduplicate-disabled-375350.invalid
View source保存された類似ドメイン:695 件
695 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
duplicate-disabled-375350.invalid
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
duplicate-disabled-375350.invalid)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.