VirusTotal
11 / 91 engine detections
Відкрити звіт“TG Meet”
фішинг: meetappbot.online — Контент недоступний (HTTP 404). Зведення доказів: VirusTotal 11/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, Forcepoint…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
11 / 91 engine detections
Відкрити звіт16 community references
Відкрити звіт80/100
Відкрити звітNo threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain meetappbot.online was registered on May 08, 2026 through NameCheap, Inc. and is hosted on a Hetzner Online GmbH server in Finland (IP 95.217.98.125). The authoritative nameservers are dns1.registrar-servers.com and dns2.registrar-servers.com. The site serves HTTP 200 responses and presents the page title "TG Meet" under a valid Let's Encrypt (R13) certificate. Infrastructure analysis shows a Gridinsoft trust score of 0/100, indicating a highly untrusted host. The domain appears on three public blocklists and is actively blocked by PhishDestroy, MetaMask, and SEAL. AlienVault OTX lists the domain in one threat‑intelligence pulse, and three independent security blocklists have flagged it. VirusTotal scanned the site with 92 vendors and reported no detections, but the lack of detections does not constitute evidence of safety. Current intelligence does not reveal the specific payload or credential‑harvesting mechanisms employed, and the page content has not been publicly analyzed. Defenders should block the domain at the network perimeter, monitor DNS queries for the associated IP and nameservers, and treat any credentials entered on the site as compromised. Ongoing observation of the domain’s activity and rapid response to any emerging indicators are recommended.
Last checked
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.
dns2.registrar-servers.comeforward1.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
034086b630dd3a1af66497ab5eb4242792dd6bf320be35807d722e1975ed075fwww.meetappbot.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.meetappbot.onlineDomain recordThe original observation time is not recorded for these hostnames.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
http_other: raw=http_404; http=404; via=http_proxy
meetappbot.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
No threat flag
View source16 community references
View source11/91 engine detections
View sourcemeetappbot.online
View sourceПовідомив 1 учасник спільноти; уперше помічено 08.05.2026
Listed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
meetappbot.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.