This domain, invitemeetings.online, operates as a fake login portal designed to harvest user credentials through deceptive authentication interfaces. Analysis indicates the site mimics legitimate meeting or collaboration platforms, tricking visitors into entering sensitive login details such as usernames, passwords, or corporate credentials. The stolen data is typically exploited for unauthorized account access, identity theft, or further phishing campaigns targeting organizational networks. The threat is particularly insidious due to its polished appearance, which closely resembles trusted services, making it difficult for users to detect without technical scrutiny. Infrastructure analysis reveals multiple high-confidence indicators of malicious activity. The domain was registered on March 25, 2026, through HOSTINGER operations, UAB, a registrar frequently associated with phishing infrastructure. It resolves to the IP address 187.77.27.91, which has been linked to other fraudulent domains in recent months. Security vendors on VirusTotal have flagged this domain as malicious, with 16 out of 95 engines detecting it as a phishing threat. Additionally, the domain appears on four independent security blocklists and is actively blocked by MetaMask, PhishDestroy, SEAL, and InversionDNS, further confirming its fraudulent nature. The creation date, combined with the rapid flagging by security systems, suggests a deliberate and short-lived campaign designed to evade detection. If you or someone in your organization visited invitemeetings.online, immediate action is required to mitigate potential damage. First, disconnect the affected device from the network to prevent any ongoing data exfiltration. Reset all credentials entered on the site, prioritizing accounts with elevated permissions or access to sensitive systems. Enable multi-factor authentication (MFA) on all critical accounts to add an additional layer of security. Monitor financial and communication platforms for unauthorized activity, as compromised credentials may be used in follow-up attacks. Finally, report the incident to your organization’s security team or a trusted cybersecurity provider to conduct a forensic analysis and ensure no residual threats remain on the device.
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:08:51 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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='invitemeetings.online', port=80): Max retries exceeded with url: / (Caused by NewConnectio
invitemeetings.online
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
