City: unknown
Region: unknown
Country: Germany
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.169.3.44
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14857
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.169.3.44. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012600 1800 900 604800 86400
;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 00:00:31 CST 2025
;; MSG SIZE rcvd: 10544.3.169.134.in-addr.arpa domain name pointer cc-3404-101-r6s7-po11.rz.tu-bs.de.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
44.3.169.134.in-addr.arpa name = cc-3404-101-r6s7-po11.rz.tu-bs.de.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 183.91.3.214 | attackspambots | 20/2/9@23:48:12: FAIL: Alarm-Network address from=183.91.3.214 ... |
2020-02-10 21:13:15 |
| 119.161.98.141 | attackbots | Microsoft SQL Server User Authentication Brute Force Attempt, PTR: PTR record not found |
2020-02-10 20:33:59 |
| 202.53.82.82 | attackspam | Feb 10 05:49:04 hell sshd[14189]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.53.82.82 Feb 10 05:49:06 hell sshd[14189]: Failed password for invalid user supervisor from 202.53.82.82 port 56785 ssh2 ... |
2020-02-10 20:31:04 |
| 51.79.140.64 | attackbots | Feb 10 03:16:00 ns4 sshd[8886]: reveeclipse mapping checking getaddrinfo for ip-51-79-140.eu [51.79.140.64] failed - POSSIBLE BREAK-IN ATTEMPT! Feb 10 03:16:00 ns4 sshd[8886]: Invalid user alw from 51.79.140.64 Feb 10 03:16:00 ns4 sshd[8886]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.140.64 Feb 10 03:16:02 ns4 sshd[8886]: Failed password for invalid user alw from 51.79.140.64 port 35118 ssh2 Feb 10 03:36:16 ns4 sshd[11483]: reveeclipse mapping checking getaddrinfo for ip-51-79-140.eu [51.79.140.64] failed - POSSIBLE BREAK-IN ATTEMPT! Feb 10 03:36:16 ns4 sshd[11483]: Invalid user bjg from 51.79.140.64 Feb 10 03:36:16 ns4 sshd[11483]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.140.64 Feb 10 03:36:18 ns4 sshd[11483]: Failed password for invalid user bjg from 51.79.140.64 port 33640 ssh2 Feb 10 03:39:14 ns4 sshd[11800]: reveeclipse mapping checking getaddrinfo for ip-51-........ ------------------------------- |
2020-02-10 21:02:50 |
| 218.104.231.2 | attackspambots | Feb 10 11:21:44 ns382633 sshd\[23340\]: Invalid user aul from 218.104.231.2 port 54198 Feb 10 11:21:44 ns382633 sshd\[23340\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.104.231.2 Feb 10 11:21:47 ns382633 sshd\[23340\]: Failed password for invalid user aul from 218.104.231.2 port 54198 ssh2 Feb 10 11:46:59 ns382633 sshd\[27809\]: Invalid user htd from 218.104.231.2 port 55876 Feb 10 11:46:59 ns382633 sshd\[27809\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.104.231.2 |
2020-02-10 20:50:58 |
| 195.95.147.98 | attackspam | " " |
2020-02-10 20:46:59 |
| 167.114.152.139 | attackbotsspam | Feb 10 07:23:18 marvibiene sshd[8346]: Invalid user mgq from 167.114.152.139 port 53398 Feb 10 07:23:18 marvibiene sshd[8346]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.152.139 Feb 10 07:23:18 marvibiene sshd[8346]: Invalid user mgq from 167.114.152.139 port 53398 Feb 10 07:23:21 marvibiene sshd[8346]: Failed password for invalid user mgq from 167.114.152.139 port 53398 ssh2 ... |
2020-02-10 20:42:28 |
| 45.76.249.188 | attack | [portscan] tcp/22 [SSH] in blocklist.de:'listed [ssh]' *(RWIN=65535)(02101252) |
2020-02-10 20:44:33 |
| 106.13.123.29 | attackbots | $f2bV_matches |
2020-02-10 21:13:38 |
| 54.37.159.12 | attack | Feb 10 07:38:29 plusreed sshd[9739]: Invalid user wbh from 54.37.159.12 ... |
2020-02-10 20:53:00 |
| 182.253.61.19 | attack | Port 22 Scan, PTR: PTR record not found |
2020-02-10 20:49:43 |
| 23.94.153.186 | attackbots | Automatic report - Port Scan |
2020-02-10 20:55:33 |
| 115.112.60.46 | attackspam | SSH bruteforce |
2020-02-10 21:06:33 |
| 123.207.246.197 | attackspambots | WordPress login Brute force / Web App Attack on client site. |
2020-02-10 20:45:40 |
| 123.31.47.20 | attack | 2020-02-10T07:19:08.829943vostok sshd\[11315\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.31.47.20 user=root | Triggered by Fail2Ban at Vostok web server |
2020-02-10 20:33:22 |