The domain remittix.foundation was registered on October 15, 2025 through NameCheap, Inc. and is currently offline. DNS resolution points to the address 66.33.60.130, which belongs to Amazon.com, Inc. (AS16509) and is geolocated in the United States. The authoritative nameservers are dns1.registrar-servers.com and dns2.registrar-servers.com. No TLS certificate is presented, indicating that the site was served over plain HTTP. The page title retrieved during the brief observation was "1 new message," and the site is documented as impersonating the Chase brand.
Analysis of the malicious payload identifies a Wallet Connect Abuse drainer kit, classifying the operation as a wallet/seed phishing attempt aimed at extracting cryptocurrency credentials. Threat intelligence indicates that the domain appears on a single security blocklist and has been blocked by PhishDestroy. Gridinsoft assigns a trust score of 0 out of 100, reflecting extreme suspicion. VirusTotal reports that 12 of 95 scanned security vendors flagged the domain as malicious, providing independent confirmation of its malicious nature.
The evidence set is limited to the observed infrastructure and metadata; content of the landing page beyond the title has not been captured, and active phishing indicators such as credential‑stealing forms remain unverified. Defenders should add the domain and its IP address to network‑level blocklists, enforce TLS inspection to detect any future attempts to serve content without encryption, and monitor for any related Wallet Connect traffic patterns. Monitoring of NameCheap registrations and the specific registrar‑servers.com nameservers may reveal additional domains employing the same infrastructure. Incident response teams encountering similar wallet‑seed phishing attempts should treat any credential submissions from this domain as compromised and advise affected users to revoke and replace associated crypto wallets.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/remittix_ethStored page reference
IoC extraction recorded 2026-08-02 04:33:15 UTC
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='remittix.foundation', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
DOM Analysisanalyzed 2026年3月24日score 15/1007 brand signals
IoC Extractionscanned 2026年8月2日0 wallet · 1 Telegram IoC
Submitted URLhttp://remittix.foundation/
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:10:06 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-04-21 22:27:25 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 22:27:25 UTC → 2026-09-30 16:14:55 UTC · 3,881.79hmidpoint estimate ≈ 2026-07-11 19:21:10 UTC · precision very 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.
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.
11 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.
加密货币诈骗通常是如何运作的？
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
恶意批准 — “连接钱包”的提示会使攻击者获得无限的代币消费权限
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
(US)
