Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
网络安全情报 Registrar context
Registrar contextTrustname
Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
velora.icu is a domain on the PhishDestroy blocklist that we first saw on 2026-09-10. No impersonated brand or page content is tied to it, so the specific scheme behind it has not been identified. The site went offline on 2026-09-10, the same day we first saw it, and its DNS was still inactive when we last checked on 2026-10-19.
How the scam works
With no captured page content, the evidence does not show which scheme velora.icu ran. It does show that three independent security vendors judged the domain malicious or risky, and that it was dropped from DNS the same day it surfaced. Short, quiet lifespans like this are common with throwaway domains that briefly host lures for logins, seed phrases or crypto payments. Anyone who reached this site through an unsolicited link, an ad or a direct message should assume it was not legitimate.
Evidence
On 2026-09-10, VirusTotal showed 3 of 89 engines flagging the domain: alphaMountain.ai, Forcepoint ThreatSeeker and SOCRadar. That is a low count, but it comes from three unrelated threat-intelligence sources reaching the same conclusion on their own. The domain also appears in 2 AlienVault OTX pulses, which means other researchers have grouped it with tracked threat activity. Among the blocklists we check, only PhishDestroy currently lists it.
Infrastructure
The domain was registered on 2026-05-04 through Fewmoretaps OU d/b/a Trustname.com, about four months before it came to our attention. A gap like that often means the name was held in reserve and activated later, rather than registered on the spot for one campaign. No hosting network was identifiable because the domain no longer resolves.
What to do
Because the domain is down, the main risk now is to anyone who used it while it was live. If you entered a password there, change it everywhere you reused it and turn on app-based two-factor authentication. If you typed in a seed phrase or private key, treat that wallet as compromised and move any remaining funds to a new wallet. If you sent a payment, keep the transaction details and report them to your exchange or local authorities. Defenders should block velora.icu at DNS and proxy level and search their logs for past lookups, since the name could be reactivated.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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:12:24 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 UTC
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.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — 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.
(BY)
PhishDestroy Investigation
