The domain meets-on.online was registered on July 20, 2026 through Namecheap Inc. It resolves to the IPv4 address 192.64.119.9 and is served by the authoritative nameservers dns1.registrar-servers.com and dns2.registrar-servers.com. The domain appears on a single public blocklist and is currently listed as blocked by the PhishDestroy feed, indicating that at least one anti-phishing community has observed malicious use. VirusTotal records show that the domain was submitted for analysis and scanned by 95 AV engines, none of which returned a positive detection at the time of scanning. While the lack of detections does not prove the site to be benign, it suggests that the payload may be novel or that the content has not yet triggered existing signatures. No information on SSL/TLS configuration, HTTP response codes, Safe Browsing status, OTX mentions, or page title has been published, so the surface-level behavior of the site remains uncharacterized. The rapid creation-to-activation timeline (one day between registration and first appearance on blocklists) is consistent with a “drop-and-run” phishing infrastructure that leverates freshly-registered domains to evade reputation-based controls. Defenders should consider adding the IPv4 address 192.64.119.9 to outbound and inbound deny lists, enforce DNS filtering for the domain, and monitor for any future detections associated with the registrar-servers nameservers. Continuous re-scanning with multi-engine services and inclusion in internal URL reputation feeds are recommended to capture any evolving malicious payloads. Until additional telemetry such as page content, SSL certificates, or HTTP headers becomes available, the domain should be treated as a high-confidence phishing indicator based on its blocklist presence and registrar profile.
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 22:38:41 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:38:41 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.
(US)
