城市(city): Heidelberg
省份(region): Baden-Württemberg
国家(country): Germany
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.155.38.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37872
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.155.38.1. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021300 1800 900 604800 86400
;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 16:44:15 CST 2025
;; MSG SIZE rcvd: 105
1.38.155.134.in-addr.arpa domain name pointer gw-38-1.rz.uni-mannheim.de.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
1.38.155.134.in-addr.arpa name = gw-38-1.rz.uni-mannheim.de.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 195.154.223.226 | attackspam | Multiple SSH auth failures recorded by fail2ban |
2019-08-17 11:25:46 |
| 211.54.40.81 | attackbotsspam | Aug 17 04:36:50 debian sshd\[4967\]: Invalid user zabbix from 211.54.40.81 port 38423 Aug 17 04:36:50 debian sshd\[4967\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.54.40.81 ... |
2019-08-17 11:54:11 |
| 36.39.22.246 | attackspam | Caught in portsentry honeypot |
2019-08-17 11:52:11 |
| 51.77.145.65 | attackbots | Aug 17 03:49:11 hosting sshd[16457]: Invalid user wright from 51.77.145.65 port 59962 ... |
2019-08-17 11:38:57 |
| 139.59.45.98 | attack | Aug 17 04:18:13 mail1 sshd\[13965\]: Invalid user foo from 139.59.45.98 port 33230 Aug 17 04:18:13 mail1 sshd\[13965\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.45.98 Aug 17 04:18:15 mail1 sshd\[13965\]: Failed password for invalid user foo from 139.59.45.98 port 33230 ssh2 Aug 17 04:33:31 mail1 sshd\[20909\]: Invalid user oozie from 139.59.45.98 port 53916 Aug 17 04:33:31 mail1 sshd\[20909\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.45.98 ... |
2019-08-17 11:57:47 |
| 167.71.10.167 | attack | port scan and connect, tcp 443 (https) |
2019-08-17 11:40:54 |
| 104.248.211.180 | attackbots | Aug 17 03:24:47 MK-Soft-VM3 sshd\[29937\]: Invalid user support from 104.248.211.180 port 40322 Aug 17 03:24:47 MK-Soft-VM3 sshd\[29937\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.211.180 Aug 17 03:24:49 MK-Soft-VM3 sshd\[29937\]: Failed password for invalid user support from 104.248.211.180 port 40322 ssh2 ... |
2019-08-17 11:41:33 |
| 177.103.163.253 | attackspam | Unauthorized connection attempt from IP address 177.103.163.253 on Port 445(SMB) |
2019-08-17 11:39:43 |
| 106.13.78.56 | attack | Aug 17 03:40:48 tuotantolaitos sshd[18431]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.78.56 Aug 17 03:40:51 tuotantolaitos sshd[18431]: Failed password for invalid user password123 from 106.13.78.56 port 37126 ssh2 ... |
2019-08-17 11:55:57 |
| 115.92.36.11 | attackbots | Invalid user ubuntu from 115.92.36.11 port 51472 |
2019-08-17 11:55:37 |
| 200.233.138.102 | attackspam | Unauthorized connection attempt from IP address 200.233.138.102 on Port 445(SMB) |
2019-08-17 11:28:53 |
| 2.32.113.118 | attack | "Fail2Ban detected SSH brute force attempt" |
2019-08-17 12:00:36 |
| 139.198.5.79 | attackbots | Aug 16 20:31:08 TORMINT sshd\[25612\]: Invalid user admin from 139.198.5.79 Aug 16 20:31:08 TORMINT sshd\[25612\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.5.79 Aug 16 20:31:10 TORMINT sshd\[25612\]: Failed password for invalid user admin from 139.198.5.79 port 58968 ssh2 ... |
2019-08-17 11:29:48 |
| 142.93.174.47 | attack | Automated report - ssh fail2ban: Aug 17 03:08:14 wrong password, user=bao, port=36180, ssh2 Aug 17 03:41:23 authentication failure Aug 17 03:41:25 wrong password, user=password, port=49154, ssh2 |
2019-08-17 11:38:09 |
| 112.252.31.28 | attack | Port Scan: TCP/80 |
2019-08-17 12:08:42 |