城市(city): unknown
省份(region): unknown
国家(country): Russian Federation (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 80.80.194.214
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52490
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;80.80.194.214. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012901 1800 900 604800 86400
;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 30 04:24:49 CST 2025
;; MSG SIZE rcvd: 106Host 214.194.80.80.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 214.194.80.80.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 151.80.155.98 | attack | Nov 1 05:58:28 tux-35-217 sshd\[25869\]: Invalid user ulva from 151.80.155.98 port 46188 Nov 1 05:58:28 tux-35-217 sshd\[25869\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.155.98 Nov 1 05:58:30 tux-35-217 sshd\[25869\]: Failed password for invalid user ulva from 151.80.155.98 port 46188 ssh2 Nov 1 06:02:09 tux-35-217 sshd\[25876\]: Invalid user admin123 from 151.80.155.98 port 55474 Nov 1 06:02:09 tux-35-217 sshd\[25876\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.155.98 ... |
2019-11-01 13:21:39 |
| 77.40.3.190 | attackspam | Nov 1 02:09:43 heicom postfix/smtpd\[2873\]: warning: unknown\[77.40.3.190\]: SASL LOGIN authentication failed: authentication failure Nov 1 02:09:46 heicom postfix/smtpd\[2801\]: warning: unknown\[77.40.3.190\]: SASL LOGIN authentication failed: authentication failure Nov 1 03:45:15 heicom postfix/smtpd\[28694\]: warning: unknown\[77.40.3.190\]: SASL LOGIN authentication failed: authentication failure Nov 1 03:45:18 heicom postfix/smtpd\[28696\]: warning: unknown\[77.40.3.190\]: SASL LOGIN authentication failed: authentication failure Nov 1 03:56:19 heicom postfix/smtpd\[29610\]: warning: unknown\[77.40.3.190\]: SASL LOGIN authentication failed: authentication failure ... |
2019-11-01 12:47:29 |
| 45.136.111.109 | attackbots | Nov 1 04:55:31 mc1 kernel: \[3866849.323364\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.111.109 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=16537 PROTO=TCP SPT=44108 DPT=33483 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 1 04:58:23 mc1 kernel: \[3867021.033694\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.111.109 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=14899 PROTO=TCP SPT=44108 DPT=33303 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 1 05:00:13 mc1 kernel: \[3867130.782759\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.111.109 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=36620 PROTO=TCP SPT=44108 DPT=33397 WINDOW=1024 RES=0x00 SYN URGP=0 ... |
2019-11-01 13:06:57 |
| 104.236.122.193 | attackbotsspam | SSH login attempts |
2019-11-01 13:25:37 |
| 157.230.129.73 | attackbots | 2019-11-01T04:58:07.701162shield sshd\[9730\]: Invalid user xiaozhang\#@! from 157.230.129.73 port 52731 2019-11-01T04:58:07.706566shield sshd\[9730\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.129.73 2019-11-01T04:58:09.464829shield sshd\[9730\]: Failed password for invalid user xiaozhang\#@! from 157.230.129.73 port 52731 ssh2 2019-11-01T05:01:53.858846shield sshd\[9936\]: Invalid user Cisco12345 from 157.230.129.73 port 43799 2019-11-01T05:01:53.864706shield sshd\[9936\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.129.73 |
2019-11-01 13:03:18 |
| 109.202.117.32 | attackbots | ET SCAN Potential SSH Scan - port: 22 proto: TCP cat: Attempted Information Leak |
2019-11-01 12:59:00 |
| 81.22.45.190 | attackbots | Nov 1 05:50:30 h2177944 kernel: \[5459547.395224\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.190 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=39733 PROTO=TCP SPT=46310 DPT=38676 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 1 05:51:40 h2177944 kernel: \[5459617.218922\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.190 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=12201 PROTO=TCP SPT=46310 DPT=39240 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 1 05:55:10 h2177944 kernel: \[5459827.748916\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.190 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=41250 PROTO=TCP SPT=46310 DPT=39213 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 1 06:03:37 h2177944 kernel: \[5460334.451515\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.190 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=27202 PROTO=TCP SPT=46310 DPT=38703 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 1 06:04:58 h2177944 kernel: \[5460415.157915\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.190 DST=85.214.117.9 |
2019-11-01 13:09:25 |
| 14.230.150.111 | attackbots | Connection by 14.230.150.111 on port: 139 got caught by honeypot at 11/1/2019 3:56:12 AM |
2019-11-01 12:54:08 |
| 219.249.133.74 | attackbotsspam | 5555/tcp 5555/tcp [2019-10-07/11-01]2pkt |
2019-11-01 12:52:34 |
| 52.81.126.101 | attackbotsspam | Oct 29 12:29:52 vzhost sshd[4121]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-81-126-101.cn-north-1.compute.amazonaws.com.cn user=r.r Oct 29 12:29:54 vzhost sshd[4121]: Failed password for r.r from 52.81.126.101 port 40598 ssh2 Oct 29 13:00:22 vzhost sshd[18664]: Invalid user confluence from 52.81.126.101 Oct 29 13:00:22 vzhost sshd[18664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-81-126-101.cn-north-1.compute.amazonaws.com.cn Oct 29 13:00:25 vzhost sshd[18664]: Failed password for invalid user confluence from 52.81.126.101 port 58880 ssh2 Oct 29 13:04:55 vzhost sshd[20693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-81-126-101.cn-north-1.compute.amazonaws.com.cn user=r.r Oct 29 13:04:57 vzhost sshd[20693]: Failed password for r.r from 52.81.126.101 port 41064 ssh2 Oct 29 13:09:29 vzhost sshd[22870]: pam_unix(ss........ ------------------------------- |
2019-11-01 13:23:16 |
| 177.170.172.154 | attackspambots | Oct 29 10:32:20 datentool sshd[19042]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.170.172.154 user=r.r Oct 29 10:32:22 datentool sshd[19042]: Failed password for r.r from 177.170.172.154 port 57620 ssh2 Oct 29 10:53:16 datentool sshd[19165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.170.172.154 user=r.r Oct 29 10:53:17 datentool sshd[19165]: Failed password for r.r from 177.170.172.154 port 33552 ssh2 Oct 29 11:02:00 datentool sshd[19232]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.170.172.154 user=r.r Oct 29 11:02:02 datentool sshd[19232]: Failed password for r.r from 177.170.172.154 port 47060 ssh2 Oct 29 11:07:21 datentool sshd[19265]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.170.172.154 user=r.r Oct 29 11:07:23 datentool sshd[19265]: Failed password for r.r from 177......... ------------------------------- |
2019-11-01 13:20:14 |
| 107.172.155.179 | attackbots | Automatic report - Banned IP Access |
2019-11-01 12:48:22 |
| 64.52.173.219 | attack | Oct 29 06:09:18 sanyalnet-cloud-vps3 sshd[16856]: Connection from 64.52.173.219 port 61499 on 45.62.248.66 port 22 Oct 29 06:09:18 sanyalnet-cloud-vps3 sshd[16856]: Did not receive identification string from 64.52.173.219 Oct 29 06:09:18 sanyalnet-cloud-vps3 sshd[16857]: Connection from 64.52.173.219 port 61534 on 45.62.248.66 port 22 Oct 29 06:09:21 sanyalnet-cloud-vps3 sshd[16857]: reveeclipse mapping checking getaddrinfo for 219.173.52.64.in-addr.arpa [64.52.173.219] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 29 06:09:21 sanyalnet-cloud-vps3 sshd[16857]: Invalid user admin from 64.52.173.219 Oct 29 06:09:21 sanyalnet-cloud-vps3 sshd[16857]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.52.173.219 Oct 29 06:09:23 sanyalnet-cloud-vps3 sshd[16857]: Failed none for invalid user admin from 64.52.173.219 port 61534 ssh2 Oct 29 06:09:26 sanyalnet-cloud-vps3 sshd[16857]: Failed password for invalid user admin from 64.52.173.219 port........ ------------------------------- |
2019-11-01 13:11:16 |
| 211.103.237.82 | attackspam | 1433/tcp 1433/tcp [2019-10-24/11-01]2pkt |
2019-11-01 12:49:46 |
| 159.65.136.141 | attack | 2019-11-01T04:47:27.536858shield sshd\[9154\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.136.141 user=root 2019-11-01T04:47:28.763949shield sshd\[9154\]: Failed password for root from 159.65.136.141 port 41354 ssh2 2019-11-01T04:51:47.742872shield sshd\[9441\]: Invalid user User from 159.65.136.141 port 51562 2019-11-01T04:51:47.747563shield sshd\[9441\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.136.141 2019-11-01T04:51:49.666448shield sshd\[9441\]: Failed password for invalid user User from 159.65.136.141 port 51562 ssh2 |
2019-11-01 12:55:52 |