The domain serbaseru.online poses an elevated risk as a confirmed brand impersonation threat specifically targeting Base, a well-known cryptocurrency platform. This type of attack typically aims to trick users into connecting their wallets or revealing sensitive information under the guise of a legitimate service. The domain was taken offline after being identified as malicious, but its history and infrastructure reveal persistent criminal intent.
Technical indicators for serbaseru.online are deeply concerning. VirusTotal flags it with 18 out of 95 security vendors detecting malicious activity, and it appears on one security blocklist. The domain was registered through NameCheap, Inc., an ICANN-accredited registrar, and was created on December 02, 2025, giving it a very short lifespan. It resolves to IP address 209.74.67.31, which may host additional threats. The page title, "Index of /", suggests a default directory listing, often used by attackers to host multiple fraudulent pages. No SSL certificate was found, further indicating a lack of security and legitimacy.
To protect against this brand impersonation scheme, users should never interact with the domain serbaseru.online or any unsolicited communications referencing it. Verify any Base-related links by manually typing the official URL (base.org) into the browser. If you have already connected a wallet or entered credentials, revoke all permissions immediately and transfer assets to a new, secure wallet. Report the domain to cybersecurity authorities and the Base team to help prevent further victimization. Stay vigilant against similar phishing tactics that exploit trusted brand names.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='serbaseru.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:11:07 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-13 22:18:28 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-13 22:18:28 UTC → 2026-09-30 16:14:55 UTC · 2,609.94hmidpoint estimate ≈ 2026-08-07 07:16:41 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.
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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(US)
