Analysis of cryptobridge.online indicates the site was registered through NameCheap, Inc. on July 31, 2025 and is hosted on Amazon’s AS16509 network at IP 216.198.79.65, a United States address. The page title “CryptoBridge - Secure Wallet Connection Platform” suggests a cryptocurrency‑related service, and the intelligence tags the campaign as a “Fake Airdrop” impersonating Ethereum. No TLS certificate was observed, meaning the site was served over plain HTTP. VirusTotal recorded a single positive detection out of 95 scanned vendors, confirming at least one security product identified malicious behavior.
The domain is currently offline, and it has been added to four independent blocklists, specifically PhishDestroy, Polkadot, Enkrypt, and Codeesura. Nameservers are dns1.registrar-servers.com and dns2.registrar-servers.com, typical of the registrar’s default configuration. The available evidence confirms that the infrastructure is actively leveraged for a brand‑impersonation campaign, but the limited detection count suggests that many scanners have not yet flagged the site, possibly due to its short lifespan or evasion techniques.
No additional artifacts such as malicious payloads, credential‑harvesting forms, or redirect chains have been disclosed, leaving the precise attack vector uncertain. Defenders should update URL filtering policies to block cryptobridge.online and its associated IP address, enforce TLS‑only connections for cryptocurrency services, and monitor for any resurgence of the domain or similar patterns using the same registrar or hosting ASN. Continuous threat‑intel feeds should be consulted for new detections, and any inbound traffic to the listed IP should be inspected for anomalous request patterns consistent with airdrop‑style phishing attempts.
DOM Analysisanalyzed 2026年3月24日score 15/1004 brand signals
Submitted URLhttp://cryptobridge.online/
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-19 01:08:14 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-04-09 04:44:11 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-09 04:44:11 UTC → 2026-09-30 16:14:55 UTC · 4,187.51hmidpoint estimate ≈ 2026-07-05 10:29:33 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.
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='cryptobridge.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
cryptobridge.online
保存済みの結果
到達不能
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
詐欺による金銭の返還を装った詐欺 — 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.
(US)
