VirusTotal
9 / 91 engine detections
Відкрити звіт“YogaMonk – Online Yoga Classes”
підробка під Across: yogamonk.online — Контент недоступний. Зведення доказів: VirusTotal 9/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Fortinet); URLQuery…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
9 / 91 engine detections
Відкрити звіт1 threat-system alert
Відкрити звітchecked — no match recorded
no community references
Відкрити звітprovider verdict: clean
Відкрити звіт14 перевірено — блокувань немає
No threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | yogamonk.online |
malicious | Sinkholed |
PhishDestroy threat report
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.
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.
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.
ns1.ultahost.comns2.ultahost.comns3.ultahost.comns4.ultahost.commail.yogamonk.onlinepriority 10yogamonk.onlinepriority 15Location describes the IP network.
566d56c73a096d1fdf842d3ca01305579087841e1ebc8e5379562edf63ecf26ewww.yogamonk.onlineSaved 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 recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of yogamonk.online · checked Mar 11, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
0→1
9/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourceyogamonk.online
View sourcePD-20260311-80F38D
Повідомив 1 учасник спільноти; уперше помічено 11.03.2026
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
yogamonk.online
PD-20260311-80F38D Recipient: abuse@first-colo.net Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
yogamonk.online)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.