城市(city): unknown
省份(region): unknown
国家(country): China
运营商(isp): China Unicom
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 39.64.144.37
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4674
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;39.64.144.37. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025062901 1800 900 604800 86400
;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jun 30 04:17:52 CST 2025
;; MSG SIZE rcvd: 105Host 37.144.64.39.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 37.144.64.39.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 183.236.248.227 | attack | Feb 8 15:23:35 debian-2gb-nbg1-2 kernel: \[3431055.312850\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=183.236.248.227 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0xE0 TTL=49 ID=36286 PROTO=TCP SPT=39933 DPT=23 WINDOW=32997 RES=0x00 SYN URGP=0 |
2020-02-09 04:15:28 |
| 103.38.14.41 | attackbotsspam | Lines containing failures of 103.38.14.41 Feb 7 08:34:27 keyhelp sshd[11482]: User support from 103.38.14.41 not allowed because a group is listed in DenyGroups Feb 7 08:34:27 keyhelp sshd[11482]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.38.14.41 user=support Feb 7 08:34:29 keyhelp sshd[11482]: Failed password for invalid user support from 103.38.14.41 port 11948 ssh2 Feb 7 08:34:29 keyhelp sshd[11482]: Connection closed by invalid user support 103.38.14.41 port 11948 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=103.38.14.41 |
2020-02-09 04:47:43 |
| 80.82.77.245 | attack | 80.82.77.245 was recorded 12 times by 10 hosts attempting to connect to the following ports: 53,120. Incident counter (4h, 24h, all-time): 12, 125, 20270 |
2020-02-09 04:48:13 |
| 106.13.88.44 | attackspambots | Feb 8 19:09:33 legacy sshd[28291]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.88.44 Feb 8 19:09:35 legacy sshd[28291]: Failed password for invalid user ohi from 106.13.88.44 port 58708 ssh2 Feb 8 19:13:30 legacy sshd[28486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.88.44 ... |
2020-02-09 04:17:27 |
| 37.49.226.50 | attackspam | (Feb 8) LEN=40 TTL=57 ID=22313 TCP DPT=8080 WINDOW=55868 SYN (Feb 8) LEN=40 TTL=57 ID=62870 TCP DPT=8080 WINDOW=55868 SYN (Feb 8) LEN=40 TTL=57 ID=22504 TCP DPT=8080 WINDOW=19786 SYN (Feb 7) LEN=40 TTL=57 ID=23245 TCP DPT=8080 WINDOW=47442 SYN (Feb 7) LEN=40 TTL=57 ID=28082 TCP DPT=8080 WINDOW=24676 SYN (Feb 6) LEN=40 TTL=57 ID=62643 TCP DPT=8080 WINDOW=24676 SYN (Feb 6) LEN=40 TTL=57 ID=44574 TCP DPT=8080 WINDOW=47442 SYN (Feb 6) LEN=40 TTL=57 ID=1179 TCP DPT=8080 WINDOW=47442 SYN (Feb 3) LEN=40 TTL=57 ID=27194 TCP DPT=8080 WINDOW=24676 SYN (Feb 3) LEN=40 TTL=57 ID=3354 TCP DPT=8080 WINDOW=8018 SYN (Feb 3) LEN=40 TTL=57 ID=14967 TCP DPT=8080 WINDOW=40914 SYN (Feb 2) LEN=40 TTL=57 ID=59437 TCP DPT=8080 WINDOW=57234 SYN (Feb 2) LEN=40 TTL=57 ID=2242 TCP DPT=8080 WINDOW=57234 SYN |
2020-02-09 04:44:28 |
| 109.115.127.219 | attackbots | Feb 8 14:22:42 yesfletchmain sshd\[18108\]: User pi from 109.115.127.219 not allowed because not listed in AllowUsers Feb 8 14:22:42 yesfletchmain sshd\[18107\]: User pi from 109.115.127.219 not allowed because not listed in AllowUsers Feb 8 14:22:42 yesfletchmain sshd\[18107\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.115.127.219 user=pi Feb 8 14:22:42 yesfletchmain sshd\[18108\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.115.127.219 user=pi Feb 8 14:22:44 yesfletchmain sshd\[18107\]: Failed password for invalid user pi from 109.115.127.219 port 40030 ssh2 ... |
2020-02-09 04:53:40 |
| 45.83.65.191 | attackspambots | trying to access non-authorized port |
2020-02-09 04:17:44 |
| 140.143.97.110 | attackspambots | Feb 8 10:32:46 auw2 sshd\[27915\]: Invalid user jen from 140.143.97.110 Feb 8 10:32:46 auw2 sshd\[27915\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.97.110 Feb 8 10:32:48 auw2 sshd\[27915\]: Failed password for invalid user jen from 140.143.97.110 port 37656 ssh2 Feb 8 10:33:42 auw2 sshd\[28006\]: Invalid user kpo from 140.143.97.110 Feb 8 10:33:42 auw2 sshd\[28006\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.97.110 |
2020-02-09 04:57:31 |
| 128.74.89.74 | attackspam | Automatic report - Port Scan Attack |
2020-02-09 04:17:00 |
| 144.217.47.174 | attack | Feb 8 17:43:34 firewall sshd[6289]: Invalid user hnw from 144.217.47.174 Feb 8 17:43:37 firewall sshd[6289]: Failed password for invalid user hnw from 144.217.47.174 port 57761 ssh2 Feb 8 17:48:04 firewall sshd[6434]: Invalid user uov from 144.217.47.174 ... |
2020-02-09 04:57:07 |
| 185.173.35.33 | attackspambots | 30303/tcp 5916/tcp 873/tcp... [2019-12-11/2020-02-08]42pkt,33pt.(tcp) |
2020-02-09 04:38:14 |
| 90.59.57.168 | attackbotsspam | Feb 8 20:24:04 PAR-182295 sshd[1211587]: Failed password for invalid user mej from 90.59.57.168 port 50836 ssh2 Feb 8 20:49:52 PAR-182295 sshd[1226894]: Failed password for invalid user uls from 90.59.57.168 port 56552 ssh2 Feb 8 21:12:16 PAR-182295 sshd[1240289]: Failed password for invalid user rng from 90.59.57.168 port 47216 ssh2 |
2020-02-09 04:27:08 |
| 164.132.46.197 | attackspam | Feb 8 21:38:05 MK-Soft-VM8 sshd[17964]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.46.197 Feb 8 21:38:07 MK-Soft-VM8 sshd[17964]: Failed password for invalid user uqp from 164.132.46.197 port 35960 ssh2 ... |
2020-02-09 04:55:04 |
| 140.249.22.238 | attackspam | $f2bV_matches |
2020-02-09 05:03:59 |
| 113.23.57.78 | attackspambots | 20/2/8@09:22:53: FAIL: IoT-Telnet address from=113.23.57.78 ... |
2020-02-09 04:46:42 |