Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
安全信号
Scamadviser Warnings1/100
The identity of the owner of the website is hidden on WHOIS The Tranco rank (how much traffic) is rather low The server of the site has several low reviewed other websites The age of this site is (very) young. Spam has been associated with this site by iQ Abuse Scan
We found a valid SSL certificate DNSFilter labels this site as safe
The domain dappchain.support was registered on July 11, 2025 through Unstoppable Domains Inc. It currently resolves to the IPv4 address 185.100.87.82, which is allocated to AS200651 FlokiNET ehf in Romania. No SSL certificate is presented for the domain, and DNS resolution reports a single nameserver, though the nameserver identifier is not disclosed. VirusTotal analysis shows that three of ninety‑five security vendors flagged the domain, indicating a modest level of detection across scanning engines.
The site title returned by HTTP requests is "Access Denied," suggesting the hosting endpoint is no longer serving the original content; the domain status is listed as offline and it has been blocked by the PhishDestroy mitigation service. The domain appears on one public security blocklist, and both Scamadviser (trust score 1/100) and Gridinsoft (trust score 0/100) assign it the lowest possible reputation scores. The intelligence categorizes the activity as a generic phishing campaign with an investment‑scam focus, and the risk level is elevated.
While the observable infrastructure confirms malicious intent, the exact payload, phishing kit, or targeted victim profile remain undefined due to the offline state of the site. Defenders should continue to block the domain at network borders, monitor DNS queries for the associated IP, and include the IP‑ASN pair in threat‑intel feeds. Further analysis should be triggered if the domain resurfaces or if additional URLs resolve to the same IP, as the low trust scores and vendor detections suggest a high likelihood of credential‑stealing or financial fraud.
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-19 01:11:59 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-08-11 22:13:34 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-11 22:13:34 UTC → 2026-09-30 16:14:55 UTC · 1,194.02hmidpoint estimate ≈ 2026-09-05 19:14:14 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.
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
CRDF
Gridinsoft
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
1194.02
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dappchain.support', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
dappchain.support
已保存的结果
无法访问
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(DE)
