VirusTotal
6 / 91 engine detections
打开报告“SaltSwap”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 27 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
冒充 MetaMask: saltswap.finance — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); 2…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 91 engine detections
打开报告Scan report
打开报告4 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.
PhishDestroy threat report
saltswap.finance is a phishing page that presents itself as SaltSwap, the name shown in its page title, to pass as a decentralized token-swap service. It targets DeFi users who search for SaltSwap or follow a shared link and assume they have reached the real exchange. PhishDestroy first flagged it on 2026-09-23. On 2026-10-19 the domain was still alive and serving a redirect, so visitors were still being routed onward.
Fake swap front-ends like this copy the look and wording of a known exchange so that the next step feels routine: connect your wallet to trade. The danger is in what the wallet then asks you to approve. A token allowance or signed permit can authorize the operator to move your assets later, without any further confirmation from you. Victims typically lose whatever tokens they approved, and sometimes the rest of the wallet's balance, once the attacker uses those permissions.
MetaMask and SEAL both list the domain alongside PhishDestroy. This means the two wallet-focused security groups independently treat it as a threat to crypto users. On VirusTotal, 6 of 91 engines flagged it as of 2026-10-03: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and URLQuery. That number is modest, so a clean result from a single scanner should not reassure anyone. The domain also appears in 4 AlienVault OTX threat pulses, showing that other researchers are tracking it.
The domain was registered through NameCheap, Inc. on 2026-09-22 and was detected one day later. That short gap fits a site built and launched quickly for a phishing campaign rather than a long-standing project. It sits behind Cloudflare, Inc. on an address geolocated to Canada, which hides the true origin server from visitors. The Let's Encrypt certificate only means the padlock icon is present. It says nothing about who runs the site.
If you connected a wallet to this site, use a token-approval checker right away. Revoke every allowance you granted to unfamiliar contracts, and look for any signed permits you do not recognize. If you approved anything or entered a seed phrase, move your remaining funds to a new wallet with a fresh recovery phrase. Reach SaltSwap only through links you have verified independently, never through ads or forwarded messages. Defenders should block saltswap.finance at the DNS and proxy level and watch for lookalike swap domains registered around the same time.
Last checked
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.
Edge-IP 声誉不属于此域。
felicity.ns.cloudflare.comliberty.ns.cloudflare.commx1.privateemail.compriority 10mx2.privateemail.compriority 10Location describes the IP network.
86343178b573f69b5114986366b98af65e4a2018f44a1ac22c21a13ab45c56b4Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
365bd593-92e9-4757-b81a-e2a795825086.saltswap.financeDomain recorddocs.saltswap.financeDomain recordexchange.saltswap.financeDomain recordm.saltswap.financeDomain recordsitemaps.saltswap.financeDomain recordvoting.saltswap.financeDomain recordwww.docs.saltswap.financeDomain recordwww.exchange.saltswap.financeDomain recordwww.saltswap.financeDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of saltswap.finance · checked Sep 23, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://www.saltswap.finance/; server=cloudflare
saltswap.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
0→1
No threat flag
View source6/91 engine detections
View source4 community references
View sourcePD-20260923-0528E3
Page captured
View sourcesaltswap.finance
View source已存储 79 个仿冒域名
PD-20260923-0528E3 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
saltswap.finance)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.