VirusTotal
3 / 89
“Telegram: Launch @authswagabot”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@reg.ru.
The latest stored availability evidence still shows the domain reachable; 7 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
swaga-auth.online — Erreichbar · Zugang eingeschränkt (HTTP 403). Markenidentität: Telegram; Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 3/89 (alphaMountain.ai, Fortinet, Gridinsoft); Spamhaus DBL_PHISH; PhishDestroy score 81/100. Registrar: REGRU-RU.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
3 / 89
3/14
DBL_PHISH
checked — no detections recorded
Melden23 community references
Meldenprovider verdict: clean
Meldengespeicherter Bericht
Melden Analyse abgeschlossen
MeldenChecked; no threat flag recorded
MeldenThis domain operates a credential phishing campaign designed to capture user login information through a convincing replica interface. The site leverages Cloudflare infrastructure for hosting and DDoS protection, complicating takedown efforts. With only 2 detections across 91 VirusTotal engines and minimal blocklist coverage, the threat remains significantly under-reported. Organizations should immediately block the domain at DNS and proxy layers, monitor for related infrastructure sharing the same nameservers, and submit samples to additional threat intelligence feeds to improve community detection coverage.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/authswagabotStored page referenceIoC extraction recorded 2026-07-29 02:27:49 UTC
Gespeicherte Beobachtungen zum Vergleich zwischen Crawler und Browser für diesen Host sowie eine Echtzeit-Fingerabdruckprüfung für Verkehrsverteilungssysteme im Keitaro-Stil.
nginxAnmerkung des Scanners: alive_content: raw=content_403; http=403; via=https_proxy; server=nginx
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.
Location describes the IP network.
8f959acab0cfe8a794b50de9314fed207e45b81cf79d2e62af784a8f8daa2d49autodiscover.swaga-auth.onlinemail.swaga-auth.onlineowa.swaga-auth.onlinewww.swaga-auth.onlineSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of swaga-auth.online · checked Jun 26, 2026
16 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 27.02.2026
PD-20260227-A053D1 Recipient: abuse@reg.ru Registrar: REG.RU (Russia) Policy Violations: Abuse policy + ICANN contractual obligations; phishing classified as bad-faith use in UDRP; domains may be suspended/removed Applicable Laws: Criminal Code RF Art.159 (fraud), Art.272 (illegal access), Art.273 (malware creation), Art.274.1 (critical infrastructure interference)
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