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.
3 / 89
3/14
DBL_PHISH
checked — no detections recorded
Report23 community references
Reportprovider verdict: clean
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
ReportThe domain swaga-auth.online has been assessed with an elevated risk level due to its classification as a generic phishing site. This risk assessment is based on the domain's current status and the technical indicators observed during the analysis.
Analysis indicates that swaga-auth.online has been flagged by 6 out of 95 security vendors on VirusTotal, suggesting a moderate level of detection among the security community. The domain was registered through REGRU-RU and resolves to the IP address 31.31.196.69. It was created on January 02, 2026, and currently appears on 3 security blocklists, further corroborating its malicious nature. The Gridinsoft trust score for this domain is 0 out of 100, indicating a complete lack of trustworthiness. Technologies detected on the domain include Bootstrap, Nginx, and HSTS, which are commonly used in web development but can also be employed to create convincing phishing sites.
To mitigate the risks associated with this generic phishing domain, users should avoid interacting with any links or content related to swaga-auth.online. Network administrators should update their firewall and DNS settings to block traffic to this domain and its associated IP address. Additionally, end-users should be educated on the signs of phishing, such as suspicious URLs, unexpected login requests, and the presence of untrusted SSL certificates. Regular security audits and updates to security software are recommended to ensure ongoing protection against similar threats.
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
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: 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.
Reported by 1 community member, first seen Feb 27, 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)
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive