meetng.online is an impersonation phishing page whose name drops a single letter from "meeting", the kind of near-miss spelling that slips past a quick glance at an invite link. Its listing on the MetaMask and SEAL blocklists points to crypto users as the intended audience. PhishDestroy first saw it on 2026-08-31. The site has been offline since 2026-09-16, and its DNS was still inactive when last checked on 2026-10-19.
How the scam works
Impersonation pages borrow the look of a service the victim already trusts, so the next request feels routine. A meeting-style name fits a common lure in crypto circles, where a contact sends a call link and the page then asks the visitor to sign in, enter details, connect a wallet or install something before joining. Whatever the victim hands over, whether credentials, a wallet signature or a download, goes to the operator, not the real service.
Evidence
On 2026-09-10, 15 of 89 VirusTotal engines flagged the domain, including BitDefender, Kaspersky, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is broad agreement among vendors that work independently. MetaMask and SEAL, both focused on crypto threats, list it alongside PhishDestroy. It also appears in four AlienVault OTX threat pulses, which means other researchers tracked it too.
Infrastructure
The domain was registered through Spaceship, Inc. and hosted on a Namecheap, Inc. network in the United States. It used a free Let's Encrypt certificate, so a padlock in the browser said nothing about whether the site was legitimate. It stayed reachable for about two weeks after PhishDestroy first saw it, a short lifespan typical of disposable phishing domains.
What to do
If you opened this link from a meeting invite, treat the sender's account as suspect and confirm with them through a separate channel. If you connected a wallet or signed anything, revoke token approvals with a trusted approval checker and move remaining funds to a fresh wallet if you entered a seed phrase. If you typed a password, change it and turn on 2FA. If you ran any file the page offered, scan the device and rotate credentials stored on it. Defenders should block the domain and search email and chat logs for invite links that point to it.
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.
Certificate fingerprintcb71c8cb5f6217e02e9e061609dc5a2bde273dad8a687a21472a646853254609Certificate names · 1 SANs
www.meetng.online
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-19 01:15:13 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:23:55 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:23:55 UTC → 2026-09-30 16:14:55 UTC · 353.85hmidpoint estimate ≈ 2026-09-23 07:19:25 UTC · precision 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.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.meetng.onlineDomain record
The original observation time is not recorded for these hostnames.
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.
詐欺による金銭の返還を装った詐欺 — 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)
