VirusTotal
8 / 92 engine detections
打开报告“Royal Capital”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@key-systems.net.
The latest stored availability evidence still shows the domain reachable; 5 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
冒充 Aave: royal-captal-ex.com — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 8/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky); 2…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
8 / 92 engine detections
打开报告Suspicious
打开报告Scan report
打开报告no community references
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
royal-captal-ex.com presents itself as "Royal Capital". The domain drops the second "i" from "capital" and adds an "-ex" suffix that suggests an exchange. It is aimed at crypto users who expect a trading or investment platform under that name. PhishDestroy first flagged it on 2026-10-14, and the site was still online and serving its content on 2026-10-19.
Impersonation pages like this borrow the name and look of a financial brand so visitors trust them enough to sign up, log in or fund an account. On fake trading platforms, the victim typically deposits crypto, sees a growing balance that exists only on screen, and is then asked for "taxes" or "withdrawal fees" before any payout is released. The payout never arrives. Any login details, identity documents or contact information entered are also collected and can be reused for account takeover or follow-up scams. Here the bait is the "Royal Capital" name.
Eight of 92 VirusTotal engines flagged the domain as of 2026-10-18: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, LevelBlue, SOCRadar and VIPRE. That count is modest, so many security tools will still let the page load without a warning. The wallet-security community has moved faster. Besides PhishDestroy, the domain appears on the MetaMask and SEAL blocklists, which means wallet users relying on those protections should see a warning.
The domain was registered through Key-Systems GmbH on 2026-10-12, only two days before PhishDestroy detected it. That short gap is typical of throwaway domains set up for a quick campaign. The site sits behind Cloudflare, so the Canadian address points to the network edge rather than the operator's real server. Its Let's Encrypt certificate gives the browser padlock, which proves only that the connection is encrypted, not that the site is legitimate.
Do not deposit funds or pay any "fee" this site demands to unlock a balance, because further payments will not release money. If you entered a password, change it everywhere you reused it, turn on app-based two-factor authentication, and watch for phishing that references Royal Capital. If you sent crypto, record the transaction hashes and report them to your exchange and local authorities, and ignore anyone offering to recover the funds for a fee. Defenders should block the domain at DNS and proxy level, report it to Cloudflare and Key-Systems, and watch for similar misspellings of the brand.
Last checked
Edge-IP 声誉不属于此域。
alaric.ns.cloudflare.combrynne.ns.cloudflare.comLocation describes the IP network.
8b08c49ae49baa6a48fc99e7742234966f0139afb9d76ec8a3cb0edfdf328a87Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
api.royal-captal-ex.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of royal-captal-ex.com · checked Oct 14, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://royal-captal-ex.com/https://royal-captal-ex.com/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa4a918f74e3b4a29-YYZkeep-alivegziptext/htmlWed, 14 Oct 2026 19:47:44 GMTMon, 12 Oct 2026 01:27:39 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=CgmQyZnZh%2FBL1IsZJsaXMF2h7nfw75bjC7MfLL6%2BXHH0DfMEw29FgXPIfhZEBRHJUdeTHUe2h0WMwzF5BrBqEh8u1w2gyK8NO4yrIgHawT9JDDrfEMgSHiWggQLRClz4CqE6zA7l"}]cloudflarecfCacheStatus;desc="DYNAMIC"max-age=31536000chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
redirected→live_content
content_served
未知→redirected
http_redirect
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
No threat flag
View source8/92 engine detections
View sourcePD-20261014-402809
Page captured
View sourceroyal-captal-ex.com
View source已存储 95 个仿冒域名
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
royal-captal-ex.com
PD-20261014-402809 Recipient: abuse@key-systems.net AUP & Terms of Service Violations: Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices. Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension. Applicable Legal Framework (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
royal-captal-ex.com)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.