城市(city): unknown
省份(region): unknown
国家(country): None
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 200.168.138.143
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4485
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;200.168.138.143. IN A
;; AUTHORITY SECTION:
. 524 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020050700 1800 900 604800 86400
;; Query time: 132 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu May 07 15:38:53 CST 2020
;; MSG SIZE rcvd: 119143.138.168.200.in-addr.arpa domain name pointer 200-168-138-143.speedycti.com.br.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
143.138.168.200.in-addr.arpa name = 200-168-138-143.speedycti.com.br.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 167.71.60.209 | attackspambots | SSH brute-force: detected 34 distinct usernames within a 24-hour window. |
2019-12-24 05:43:57 |
| 188.243.104.166 | attack | Unauthorized connection attempt detected from IP address 188.243.104.166 to port 23 |
2019-12-24 05:58:08 |
| 61.96.29.55 | attack | 445/tcp 1433/tcp... [2019-10-25/12-23]13pkt,2pt.(tcp) |
2019-12-24 05:44:34 |
| 77.247.108.77 | attack | Dec 23 22:58:51 debian-2gb-nbg1-2 kernel: \[791075.312369\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=77.247.108.77 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=41133 PROTO=TCP SPT=56263 DPT=5038 WINDOW=1024 RES=0x00 SYN URGP=0 |
2019-12-24 06:08:29 |
| 80.20.231.251 | attack | 2323/tcp 23/tcp... [2019-10-23/12-23]18pkt,2pt.(tcp) |
2019-12-24 05:40:24 |
| 106.38.112.62 | attackspambots | Dec 23 18:58:56 hosting sshd[11556]: Invalid user server from 106.38.112.62 port 54370 Dec 23 18:58:56 hosting sshd[11556]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.38.112.62 Dec 23 18:58:56 hosting sshd[11556]: Invalid user server from 106.38.112.62 port 54370 Dec 23 18:58:58 hosting sshd[11556]: Failed password for invalid user server from 106.38.112.62 port 54370 ssh2 ... |
2019-12-24 05:41:26 |
| 95.213.177.122 | attackspam | Dec 23 18:50:50 TCP Attack: SRC=95.213.177.122 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=240 PROTO=TCP SPT=47049 DPT=65531 WINDOW=1024 RES=0x00 SYN URGP=0 |
2019-12-24 06:04:02 |
| 159.203.201.115 | attack | Unauthorized connection attempt from IP address 159.203.201.115 on Port 3389(RDP) |
2019-12-24 05:46:43 |
| 129.150.172.40 | attackbots | Oct 9 02:40:28 yesfletchmain sshd\[13042\]: User root from 129.150.172.40 not allowed because not listed in AllowUsers Oct 9 02:40:28 yesfletchmain sshd\[13042\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.150.172.40 user=root Oct 9 02:40:30 yesfletchmain sshd\[13042\]: Failed password for invalid user root from 129.150.172.40 port 9765 ssh2 Oct 9 02:43:54 yesfletchmain sshd\[13302\]: User root from 129.150.172.40 not allowed because not listed in AllowUsers Oct 9 02:43:54 yesfletchmain sshd\[13302\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.150.172.40 user=root ... |
2019-12-24 05:47:38 |
| 45.148.10.140 | attack | 12/23/2019-16:22:14.091198 45.148.10.140 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2019-12-24 05:59:57 |
| 139.59.62.42 | attackspam | SSH bruteforce |
2019-12-24 06:11:36 |
| 163.177.40.85 | attack | MultiHost/MultiPort Probe, Scan, Hack - |
2019-12-24 05:46:25 |
| 51.68.137.13 | attack | Dec 23 21:27:37 debian-2gb-nbg1-2 kernel: \[785601.652100\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=51.68.137.13 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=237 ID=54321 PROTO=TCP SPT=34862 DPT=2377 WINDOW=65535 RES=0x00 SYN URGP=0 |
2019-12-24 06:07:06 |
| 150.242.85.64 | attackspam | " " |
2019-12-24 05:54:47 |
| 82.118.242.108 | attackbotsspam | 23.12.2019 21:35:55 Connection to port 27015 blocked by firewall |
2019-12-24 05:43:32 |