Analysis of coldcard.online indicates that the domain was registered through Namecheap Inc on August 2, 2026 and is currently resolved to the IPv4 address 45.67.84.129. The authoritative name servers listed are dns1.registrar-servers.com and dns2.registrar-servers.com, both of which are typical of the registrar’s default configuration. The domain appears on a single security blocklist and is actively blocked by the PhishDestroy filtering service, confirming that at least one external sinkhole recognizes it as malicious.
VirusTotal records show that the domain was scanned by 91 independent vendors; none of the scanners raised a detection at the time of analysis, though the absence of detections does not constitute a safety assurance. No additional public threat intelligence sources such as OTX or Google Safe Browsing have been cited for this domain, and no SSL certificate details, HTTP response codes, or page title information have been disclosed, leaving those aspects of the infrastructure unverified. The limited visibility into the hosting environment beyond the resolved IP prevents definitive attribution of the underlying server operator or geographic location.
Given the recent creation date, the active blocklist status, and the blocking by PhishDestroy, defenders should treat coldcard.online as a high‑confidence phishing indicator. Recommended mitigations include adding the domain to local deny lists, configuring network perimeter filters to drop traffic to 45.67.84.129, and monitoring for any future resolution changes or additional blocklist listings. Continuous re‑evaluation is advised as further intelligence, such as HTTP header analysis or content inspection, becomes available.
DOM Analysisanalyzed 2026年8月4日score 85/1001 brand signal
Submitted URLhttp://coldcard.online/
案件 ID
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.
Certificate fingerprint208cfa6457a1d07ef61457511d9c84db9b805c5eef5e7ba74b6038776440bff1Certificate names · 1 SANs
www.coldcard.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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:16 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-08-06 22:14:43 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-06 22:14:43 UTC → 2026-09-30 16:14:55 UTC · 1,314.00hmidpoint estimate ≈ 2026-09-03 07:14:49 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.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.coldcard.onlineDomain record
The original observation time is not recorded for these hostnames.
技术 · 4 identified
N
Node.js
Programming languages
Node.js is an open-source, cross-platform, JavaScript runtime environment that executes JavaScript code outside a web browser.
Express is a web application framework for Node.js, released as free and open-source software under the MIT License. It is designed for building web applications and APIs.
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.
