The domain meets-in.online was registered on July 20, 2026 through NameCheap, Inc. and is currently resolving to the IPv4 address 162.255.119.54. The domain is hosted on the registrar's default nameservers dns1.registrar-servers.com and dns2.registrar-servers.com. It has been flagged by the PhishDestroy detection vendor and appears on one external security blocklist, indicating that at least one security feed has identified it as malicious. No public evidence of the site’s page title, SSL certificate details, HTTP response codes, or content analysis is available, so the exact phishing payload and targeted brand remain unknown. The infrastructure analysis confirms that the domain remains active despite the blocklist entry, suggesting that the operator has not yet taken the site offline. Defenders should immediately add meets-in.online and its resolving IP address 162.255.119.54 to network deny lists and DNS filtering rules. Monitoring of DNS queries for the registrar‑provided nameservers may reveal additional related domains created by the same actor. Because the registration was performed through a widely used registrar, additional scrutiny of newly created NameCheap domains with similar creation dates is advisable. Continuous observation of threat intelligence feeds for any new detections or expanded blocklist listings will help assess whether the campaign evolves or expands to other targets. In the absence of further technical details, the recommendation is to treat the domain as a high‑confidence malicious indicator and enforce blocklisting across perimeter defenses while awaiting further forensic evidence.
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-20 10:11:36 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-20 10:11:36 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.
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)
