城市(city): Tainan
省份(region): Tainan
国家(country): Taiwan, China
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 140.116.164.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59765
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;140.116.164.139. IN A
;; AUTHORITY SECTION:
. 576 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2023051200 1800 900 604800 86400
;; Query time: 26 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 12 17:28:48 CST 2023
;; MSG SIZE rcvd: 108Host 139.164.116.140.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 139.164.116.140.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 196.52.43.51 | attackbotsspam | Port scan attempt detected by AWS-CCS, CTS, India |
2019-09-04 03:30:48 |
| 185.134.179.114 | attack | SSH/22 MH Probe, BF, Hack - |
2019-09-04 03:37:24 |
| 204.44.83.83 | attackbots | (From eric@talkwithcustomer.com) Hello belcherchiropractic.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website belcherchiropractic.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website belcherchiropractic.com, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Timing – |
2019-09-04 03:03:30 |
| 91.207.40.42 | attack | Sep 3 20:40:29 mail sshd\[20714\]: Invalid user dotblot from 91.207.40.42 Sep 3 20:40:29 mail sshd\[20714\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.207.40.42 Sep 3 20:40:30 mail sshd\[20714\]: Failed password for invalid user dotblot from 91.207.40.42 port 51406 ssh2 ... |
2019-09-04 03:25:27 |
| 49.234.185.33 | attackbotsspam | Sep 3 21:11:18 rpi sshd[12017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.185.33 Sep 3 21:11:20 rpi sshd[12017]: Failed password for invalid user ftpuser from 49.234.185.33 port 58494 ssh2 |
2019-09-04 03:34:37 |
| 41.138.104.110 | attackspambots | Automatic report - Port Scan Attack |
2019-09-04 03:29:46 |
| 121.165.136.30 | attackspam | firewall-block, port(s): 23/tcp |
2019-09-04 03:33:44 |
| 193.169.255.102 | attackbotsspam | Sep 3 21:35:11 vps647732 sshd[26510]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.169.255.102 Sep 3 21:35:13 vps647732 sshd[26510]: Failed password for invalid user utilisateur from 193.169.255.102 port 48516 ssh2 ... |
2019-09-04 03:37:00 |
| 118.89.30.90 | attack | Sep 3 20:52:42 markkoudstaal sshd[27188]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.30.90 Sep 3 20:52:44 markkoudstaal sshd[27188]: Failed password for invalid user beavis from 118.89.30.90 port 53122 ssh2 Sep 3 20:58:22 markkoudstaal sshd[27743]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.30.90 |
2019-09-04 03:02:37 |
| 34.80.133.2 | attackbots | Sep 3 20:36:15 tux-35-217 sshd\[10804\]: Invalid user wwwrun from 34.80.133.2 port 38128 Sep 3 20:36:15 tux-35-217 sshd\[10804\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.80.133.2 Sep 3 20:36:18 tux-35-217 sshd\[10804\]: Failed password for invalid user wwwrun from 34.80.133.2 port 38128 ssh2 Sep 3 20:41:00 tux-35-217 sshd\[10907\]: Invalid user reko from 34.80.133.2 port 53696 Sep 3 20:41:00 tux-35-217 sshd\[10907\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.80.133.2 ... |
2019-09-04 02:59:11 |
| 14.177.40.198 | attackbots | port scan and connect, tcp 23 (telnet) |
2019-09-04 03:18:57 |
| 23.129.64.188 | attack | $f2bV_matches |
2019-09-04 03:21:59 |
| 62.163.255.133 | attack | Too many connections or unauthorized access detected from Arctic banned ip |
2019-09-04 03:39:03 |
| 187.32.80.11 | attackbots | Jul 31 14:26:23 Server10 sshd[9071]: Invalid user Nicole from 187.32.80.11 port 46954 Jul 31 14:26:23 Server10 sshd[9071]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.32.80.11 Jul 31 14:26:25 Server10 sshd[9071]: Failed password for invalid user Nicole from 187.32.80.11 port 46954 ssh2 Jul 31 14:31:44 Server10 sshd[16240]: Invalid user teamspeak from 187.32.80.11 port 39726 Jul 31 14:31:44 Server10 sshd[16240]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.32.80.11 Jul 31 14:31:46 Server10 sshd[16240]: Failed password for invalid user teamspeak from 187.32.80.11 port 39726 ssh2 |
2019-09-04 03:17:54 |
| 186.88.6.76 | attackbotsspam | " " |
2019-09-04 03:19:17 |