城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.106.197.214
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56207
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;34.106.197.214. IN A
;; AUTHORITY SECTION:
. 416 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020021600 1800 900 604800 86400
;; Query time: 143 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 18:52:02 CST 2020
;; MSG SIZE rcvd: 118214.197.106.34.in-addr.arpa domain name pointer 214.197.106.34.bc.googleusercontent.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
214.197.106.34.in-addr.arpa name = 214.197.106.34.bc.googleusercontent.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 72.43.141.7 | attackspam | Oct 16 18:40:36 markkoudstaal sshd[30518]: Failed password for root from 72.43.141.7 port 45716 ssh2 Oct 16 18:45:23 markkoudstaal sshd[30948]: Failed password for root from 72.43.141.7 port 5970 ssh2 |
2019-10-17 01:06:55 |
| 200.194.28.116 | attackbots | Oct 16 18:35:29 tux-35-217 sshd\[14769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.194.28.116 user=root Oct 16 18:35:31 tux-35-217 sshd\[14769\]: Failed password for root from 200.194.28.116 port 41912 ssh2 Oct 16 18:35:33 tux-35-217 sshd\[14769\]: Failed password for root from 200.194.28.116 port 41912 ssh2 Oct 16 18:35:35 tux-35-217 sshd\[14769\]: Failed password for root from 200.194.28.116 port 41912 ssh2 ... |
2019-10-17 00:43:39 |
| 118.187.7.103 | attackbotsspam | Oct 16 14:20:26 meumeu sshd[15249]: Failed password for root from 118.187.7.103 port 46374 ssh2 Oct 16 14:26:14 meumeu sshd[16271]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.187.7.103 Oct 16 14:26:16 meumeu sshd[16271]: Failed password for invalid user rh from 118.187.7.103 port 48300 ssh2 ... |
2019-10-17 01:05:33 |
| 217.182.79.245 | attack | Oct 16 06:48:23 hpm sshd\[3840\]: Invalid user tspass from 217.182.79.245 Oct 16 06:48:23 hpm sshd\[3840\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=245.ip-217-182-79.eu Oct 16 06:48:24 hpm sshd\[3840\]: Failed password for invalid user tspass from 217.182.79.245 port 60764 ssh2 Oct 16 06:52:31 hpm sshd\[4150\]: Invalid user toy from 217.182.79.245 Oct 16 06:52:31 hpm sshd\[4150\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=245.ip-217-182-79.eu |
2019-10-17 01:04:02 |
| 210.133.241.200 | attackspam | Spam emails used this IP address for the URLs in their messages. This kind of spam had the following features.: - They passed the SPF authentication checks. - They used networks 210.133.240.0/22 (netname: BOOT-NET) for their SMTP servers. - They used the following domains for the email addresses and URLs.: anybodyamazed.jp, askappliance.jp, hamburgermotorboat.jp, holidayarchitectural.jp, 5dfis3r.com, 5iami22.com, d8hchg5.com, myp8tkm.com, wh422c8.com, wxzimgi.com, classificationclarity.com, swampcapsule.com, tagcorps.com, etc. - Those URLs used the following name sever pairs.: -- ns1.anyaltitude.jp and ns2 -- ns1.abandonedemigrate.com and ns2 -- ns1.greetincline.jp and ns2 -- ns1.himprotestant.jp and ns2 -- ns1.swampcapsule.com and ns2 -- ns1.yybuijezu.com and ns2 |
2019-10-17 00:54:03 |
| 116.211.118.249 | attackspam | Unauthorised access (Oct 16) SRC=116.211.118.249 LEN=40 TOS=0x10 PREC=0x40 TTL=48 ID=63926 TCP DPT=23 WINDOW=26114 SYN Unauthorised access (Oct 14) SRC=116.211.118.249 LEN=40 TOS=0x10 PREC=0x40 TTL=48 ID=55177 TCP DPT=23 WINDOW=30581 SYN |
2019-10-17 00:51:09 |
| 89.24.210.10 | attackbotsspam | postfix (unknown user, SPF fail or relay access denied) |
2019-10-17 01:13:31 |
| 196.52.43.118 | attackbotsspam | MultiHost/MultiPort Probe, Scan, Hack - |
2019-10-17 01:05:12 |
| 196.52.43.53 | attack | Automatic report - Banned IP Access |
2019-10-17 01:17:28 |
| 58.249.123.38 | attackspambots | Oct 16 18:48:34 server sshd\[32688\]: Invalid user webpop from 58.249.123.38 Oct 16 18:48:34 server sshd\[32688\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.249.123.38 Oct 16 18:48:36 server sshd\[32688\]: Failed password for invalid user webpop from 58.249.123.38 port 35654 ssh2 Oct 16 18:53:58 server sshd\[1932\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.249.123.38 user=root Oct 16 18:53:59 server sshd\[1932\]: Failed password for root from 58.249.123.38 port 44342 ssh2 ... |
2019-10-17 00:49:41 |
| 196.52.43.110 | attackspambots | MultiHost/MultiPort Probe, Scan, Hack - |
2019-10-17 00:57:53 |
| 202.124.204.22 | attackbotsspam | port scan and connect, tcp 1433 (ms-sql-s) |
2019-10-17 01:19:25 |
| 222.186.52.86 | attackspam | Oct 16 12:51:27 ny01 sshd[31158]: Failed password for root from 222.186.52.86 port 34973 ssh2 Oct 16 12:52:58 ny01 sshd[31283]: Failed password for root from 222.186.52.86 port 11161 ssh2 |
2019-10-17 00:57:21 |
| 41.38.42.52 | attack | Telnet/23 MH Probe, BF, Hack - |
2019-10-17 00:46:10 |
| 23.247.22.37 | attackbotsspam | Autoban 23.247.22.37 AUTH/CONNECT |
2019-10-17 01:02:30 |