VirusTotal
11 / 91
“TG Meet”
meetappbot.online — Contenu indisponible (HTTP 404). Usurpation de l'identité de la marque : ["telegram"]; Type d'arnaque : Generic Phishing. Résumé des preuves: VirusTotal 11/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Bureau d’enregistrement: NameCheap.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
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.
Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.
Note relative à la numérisation: http_other: raw=http_404; http=404; via=http_proxy
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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Signalé par 1 membre de la communauté ; première observation le 08/05/2026
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Template-based draft · optional AI wording assistance requires separate consent
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif