The domain yogamonk.online was registered on 11 March 2026 through HOSTINGER operations, UAB and is currently taken offline. DNS resolution points to the IPv4 address 84.200.17.184, which belongs to the German hosting provider Ultahost, Inc. (ASN214036). The authoritative nameservers are ns1.ultahost.com, ns2.ultahost.com, ns3.ultahost.com, and ns4.ultahost.com, indicating the infrastructure is fully under the Ultahost umbrella. The web server presents an Nginx stack with HTTP Strict Transport Security enabled and utilizes a Let’s Encrypt certificate (R13) for TLS termination. Google Analytics scripts were detected, suggesting some level of traffic monitoring.
The page title returned from the site was "YogaMonk – Online Yoga Classes," but no further content analysis is available. Email routing is configured with MX records for mail.yogamonk.online (priority 10) and an additional host at priority 15, confirming a functional mail subsystem. Threat intelligence flags the domain as a generic phishing site; one of ninety‑five VirusTotal scanners reported a detection, and the domain appears on a single external blocklist. PhishDestroy has already added the domain to its blocklist, and the overall risk assessment is elevated.
Defensive operators should immediately block both the domain name and the associated IP address 84.200.17.184 at perimeter devices. Continuous monitoring of Ultahost‑hosted IP ranges for similar activity is advised, as the infrastructure may be reused for related campaigns. Threat intel feeds should be updated to include the domain, its MX hosts, and the associated nameservers to prevent future resolution. Since the site is offline, evidence collection should focus on historic DNS, SSL certificate logs, and any retained traffic captures that reference the domain.
DOM Analysisanalyzed 2026年7月29日score 56/1002 brand signals
Submitted URLhttps://yogamonk.online/
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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 fingerprint566d56c73a096d1fdf842d3ca01305579087841e1ebc8e5379562edf63ecf26eCertificate names · 1 SANs
www.yogamonk.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.yogamonk.onlineDomain record
The original observation time is not recorded for these hostnames.
使用技術 · 3 identified
N
Nginx
Web serversReverse proxies
High-performance HTTP server and reverse proxy, known for stability and low resource usage.
H
HSTS
セキュリティ
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google Analytics
Analytics
Web analytics service tracking website traffic and user behavior.
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.
(LT)
