On 22 July 2026 analysts observed that the domain eightxcap.online, created on 21 February 2026 and hosted by Hostinger International Limited (AS47583) in Malaysia, was taken offline after being identified as a brand‑impersonation site targeting Ethereum. The site resolved to the IPv6 address 2a02:4780:5c:2188:0:220f:902e:b and used the generic parking nameservers ns1.dns-parking.com and ns2.dns-parking.com. No TLS certificate was presented, indicating the site was served only over HTTP. VirusTotal recorded 2 detections out of 93 scanned security vendors, confirming that at least a minority of scanners flagged the domain as malicious.
The domain appears on a single external blocklist and has been explicitly blocked by the PhishDestroy service. Gridinsoft assigned a trust score of 0 out of 100, reflecting an extremely low reputation. The only visible page title returned by the web server was the Thai string “ข้อความใหม่ 1 ข้อความ”, which provides no indication of the intended malicious payload. The intelligence does not reveal the specific luring technique, credential‑harvesting page, or any associated command‑and‑control infrastructure, so the full operational profile remains uncertain.
Defenders should continue to block eightxcap.online at perimeter filters, DNS resolvers, and endpoint protection solutions, and monitor for any future re‑registration of the same name or similar sub‑domains. Threat‑intel feeds should be updated to reflect the brand‑impersonation classification targeting Ethereum, and any alerts referencing the IPv6 address or the Hostinger parking nameservers should be investigated for potential reuse. Because the site is currently offline, active takedown is not required, but continued observation is advised to detect possible resurrection or migration to alternative hosting.
DOM Analysisanalyzed 2026年4月23日score 25/1002 brand signals
Submitted URLhttps://eightxcap.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.
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:23 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-16 22:13:40 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 22:13:40 UTC → 2026-09-30 16:14:55 UTC · 2,538.02hmidpoint estimate ≈ 2026-08-08 19:14:17 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='eightxcap.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
eightxcap.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.
PDF notice generated Notice text archived (1,164 chars)
Abuse notice text as sent to the provider
Policy Violations:
Section 3.1 of the AUP: The domain eightxcap.online is engaged in phishing activities, which directly contravenes the prohibition against illegal activities and fraud.
Section 4.2 of the TOS: The domain's operation constitutes a clear violation of the terms regarding deceptive practices, warranting immediate suspension or termination of services.
Applicable Laws (Unknown):
Computer Fraud and Abuse Act (CFAA): This U.S. law prohibits unauthorized access to computers and networks, which includes phishing schemes aimed at acquiring sensitive information.
Wire Fraud Statute (18 U.S.C. § 1343): Engaging in schemes to defraud individuals via electronic communications, such as phishing, is a violation under this statute.
CAN-SPAM Act (15 U.S.C. § 7701): This law regulates commercial email and prohibits deceptive practices, including phishing, aimed at misleading recipients.
Regulatory Note: Failure to take appropriate action against this domain may expose your organization to legal liability and regulatory scrutiny. Immediate compliance with your AUP and TOS is essential to mitigate risks associated with hosting fraudulent activities.
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.
(LT)
