VirusTotal
14 / 91
tg-verify-check.online — Letzter bekanntermaßen aktiv (HTTP 200). Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 14/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Registrar: Registrar of Domain Na….
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
The domain tg-verify-check.online was registered on 23 May 2026 through REG.RU LLC and is currently active. DNS resolution points to the IPv4 address 87.120.107.209, which geolocates to Finland and is associated with the name Mykyta Skorobohatko. The authoritative nameservers are ns1.reg.ru and ns2.reg.ru. An SSL certificate issued by Let’s Encrypt (profile E7) is present, and the web server returns HTTP 200 with the page title "Loading". The site is listed on three security blocklists and has been blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal analysis shows three of 91 security vendors flagging the domain, and Gridinsoft assigns a trust score of 0 / 100. AlienVault OTX references the domain in one threat pulse. No additional content analysis is available, so the exact phishing payload or credential‑capture mechanisms remain unknown. Given the recent registration, active hosting, low trust score, and multiple detections, defenders should treat tg-verify-check.online as high‑risk. Recommended mitigations include adding the domain to network and endpoint blocklists, monitoring DNS queries for the associated IP, and employing URL filtering to prevent user access. Continuous re‑evaluation is advised as further intelligence becomes available.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/EURegulationStored page referencehttps://t.me/StickersStored page referencehttps://t.me/TelegramTipsStored page referencehttps://t.me/TelegramTips/206Stored page referencehttps://t.me/TelegramTips/221Stored page referencehttps://t.me/Username_botStored page referencehttps://t.me/durov/142Stored page referencehttps://t.me/durov/146Stored page referencehttps://t.me/durov/172Stored page referencehttps://t.me/durov/345Stored page referencehttps://t.me/durov/40Stored page referencehttps://t.me/gifStored page referencehttps://t.me/notoscamStored page referencehttps://t.me/pressbotStored page referencehttps://t.me/publictestgroupStored page referencehttps://t.me/stickerStored page referencehttps://t.me/telegramStored page referencehttps://t.me/telegramauditionsStored page referencehttps://t.me/usernameStored page referenceIoC extraction recorded 2026-09-20 04:00:50 UTC
Gespeicherte Beobachtungen zum Vergleich zwischen Crawler und Browser für diesen Host sowie eine Echtzeit-Fingerabdruckprüfung für Verkehrsverteilungssysteme im Keitaro-Stil.
nginx/1.24.0 (Ubuntu)Anmerkung des Scanners: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.24.0 (Ubuntu)
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.
ns2.reg.ruLocation describes the IP network.
a7663ed6e06cabc6ae269ee045ab97e582e9391c9359957a04f6d8d66fc5fcb4Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
9 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.
Von 1 Community-Mitglied gemeldet; erstmals gesehen am 23.05.2026
Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Template-based draft · optional AI wording assistance requires separate consent
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt