This domain, coinbase.supportcentre.online, was observed targeting the Coinbase brand through a crypto‑scam impersonation. The site was registered on 21 February 2026 via Global Domain Group LLC and is served by the nameservers dns1.lytehosting.com, dns2.lytehosting.com, dns3.lytehosting.com, dns4.l (as listed). VirusTotal analysis returned detections from 2 of 93 scanning engines, indicating that at least two security products identified malicious behavior. The domain is listed on a single public security blocklist and has been actively blocked by the PhishDestroy mitigation service.
The page title returned by the HTTP response was “www.coinbase.supportcentre.online”, confirming the exact host name used in the malicious payload. No additional infrastructure details such as IP address, ASN, or SSL certificate information were available in the collected intelligence. As of the report date (24 July 2026) the domain is taken offline, but the presence of the registration and detection artifacts suggests that the actors behind the campaign retain the ability to launch similar impersonation sites quickly. Defenders should ensure that the fully qualified domain name is added to inbound and outbound web filtering rules, that email gateways are configured to flag URLs containing “coinbase.supportcentre.online”, and that threat‑intel feeds reflecting the two VirusTotal detections and the PhishDestroy block are kept up to date.
Continuous monitoring of new domains registered with Global Domain Group LLC and of the lytehosting.com name server range is recommended to catch potential re‑use of the same hosting infrastructure. Awareness‑raising for users regarding unsolicited messages that reference Coinbase and direct recipients to unfamiliar sub‑domains will further reduce the risk of credential compromise. Given the limited detection footprint, the domain should be treated as a high‑confidence indicator of compromise for any organization that uses Coinbase services.
DOM Analysisanalyzed 2026年3月24日score 56/1001 brand signal
ICANN OVERSIGHTRegistration: supportcentre.online
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
For the registrable domain supportcentre.online behind this subdomain, 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:14:25 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:17:53 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:53 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:24 UTC · precision 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: 5 detections
ChainPatrol
alphaMountain.ai
CRDF
ESET
Gridinsoft
カスペルスキー
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
353.95
Estimate basis
Bounded by observations
Estimate precision
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='coinbase.supportcentre.online', port=80): Max retries exceeded with url: / (Caused by NewC
coinbase.supportcentre.online
Stored observation history10
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)
