Security engines reporting a detection: 3. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
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.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='coldcard.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Aug 2, 2026 (72d · New)—Expires Aug 2, 2027
Time to First Unavailability3 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 4, 2026
DOM Analysisanalyzed Aug 4, 2026score 85/1001 brand signal
Submitted URLhttp://coldcard.online/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
45.67.84.129
Network ASN
AS152586
Organization
Kuroit
Observed location
London, GB
Server header
nginx/1.18.0 (Ubuntu)
Nameservers 2
dns1.registrar-servers.com
dns2.registrar-servers.com
Mail routing 5 MX records
eforward3.registrar-servers.compriority 10
eforward1.registrar-servers.compriority 10
eforward2.registrar-servers.compriority 10
eforward4.registrar-servers.compriority 15
eforward5.registrar-servers.compriority 20
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-08-02 18:22:21
Valid until
2026-10-31 18:22:20
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-08-04 10:02:04 UTC
Collection source
PhishDestroy collector
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 inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:12:57 UTC
RDAP registrationUnknown
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.
Technologies · 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.
Google PageSpeed Insights — mobile performance audit of coldcard.online· checked Aug 4, 2026
94
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
2.6s
Largest Contentful Paint
CLS
0.098
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Domain Status Transition2026-08-06 22:35:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-08-04 09:31:50 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 45.67.84.129.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
coldcard.online detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Aug 7, 2026
Time to First Unavailability
61 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
5 evidence signal groups linked1 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · coldcard.online
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
