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.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note: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
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Registration (base domain)supportcentre.online · Created Feb 21, 2026 (234d)
Time to First Unavailability42 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 DetectedFeb 26, 2026
DOM Analysisanalyzed Mar 24, 2026score 56/1001 brand signal
ICANN OVERSIGHTRegistration: supportcentre.online
Accreditation and RAA context
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Nameservers 1
dns4.lytehosting.com
Location describes the IP network.
Latest Classified Outcome 2026-10-13 20:21:07 UTC
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:17:27 UTC
RDAP registrationUnknown
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
Kaspersky
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
coinbase.supportcentre.online detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Apr 9, 2026
Time to First Unavailability
997 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.
3 evidence signal groups linked0 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 →
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.
Registrable-domain reportParent
Separate evidence record for the registrable domain above coinbase.supportcentre.online.
(US)
