VirusTotal
8 / 92 engine detections
打开报告“Royal Capital”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namemart.com.
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.vip — 未验证. 证据摘要: VirusTotal 8/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky); 2 external blocklist…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
8 / 92 engine detections
打开报告Suspicious
打开报告Scan report
打开报告2 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.vip is an impersonation phishing page presenting itself as "Royal Capital". The domain drops the "i" from "capital" and adds "ex", a typo-style lookalike aimed at people who expect a legitimate trading or investment platform and are drawn in by a convincing name. PhishDestroy first saw it on 2026-10-14. As of 2026-10-19 the domain is still listed as live, but its DNS no longer resolves to active page content.
Impersonation sites like this copy the branding and name of a known platform, here shown in the page title "Royal Capital", so visitors believe they are on the real service. Victims are typically asked to log in, register, or fund an account, which hands their credentials, personal details, or deposited crypto directly to the operators. Money sent to such a platform cannot be withdrawn, and stolen login details are often reused against the genuine service or other accounts.
On 2026-10-18, 8 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, LevelBlue, SOCRadar and VIPRE. Beyond PhishDestroy, the domain is listed on the MetaMask and SEAL blocklists, both focused on crypto-related threats. It also appears in 2 AlienVault OTX threat pulses.
The domain was registered on 2026-10-12 through NameMart Pte. Ltd., just two days before PhishDestroy detected it, a short lead time typical of throwaway phishing domains. It sits behind Cloudflare, Inc. at 188.114.96.3, geolocated to CA, which masks the origin server. The site used a TLS certificate from Let's Encrypt (YE1), so the browser padlock says nothing about its legitimacy.
Do not visit or interact with royal-captal-ex.vip, and reach any trading platform only through an address you have verified yourself. If you entered a password, change it immediately on the real service and anywhere you reused it, then enable two-factor authentication. If you sent funds, record the transaction details and report them to your exchange and local authorities, and treat anyone offering to recover the money as a likely follow-up scam. Security teams should block the domain at DNS and proxy level, add it to mail and web filters, and watch for similar misspellings of the Royal Capital name.
Last checked
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.
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.
Edge-IP 声誉不属于此域。
alaric.ns.cloudflare.combrynne.ns.cloudflare.comLocation describes the IP network.
9c55e01bd76061ed235484badb8dab07106dcf4085b3e25ce4801355d43cbbe1Saved 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.vipDomain recorddw.royal-captal-ex.vipDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of royal-captal-ex.vip · 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.vip/https://royal-captal-ex.vip/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa4a918f9e9bde9bf-EWRkeep-alivegziptext/htmlWed, 14 Oct 2026 19:47:45 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=O3Ln8c95LDLqeDXqkvw4PCHmq2C9ArHqduzJRbpkVU9AUBN0RwZNdOh%2B1XwLmKpnt2BIqawgYCoH6gjKSEjkhkvTy0XldbYrnypCW99hk%2FzqJulGVCz0%2F0yB0QkNaDZ%2BWUbBm9FcloudflarecfCacheStatus;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.
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
可访问
No threat flag
View source8/92 engine detections
View sourcePD-20261014-4355B5
2 community references
View sourcePage captured
View sourceroyal-captal-ex.vip
View source已存储 95 个仿冒域名
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
royal-captal-ex.vip
PD-20261014-4355B5 Recipient: abuse@namemart.com 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.vip)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.