Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: China

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 116.171.70.54
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13481
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;116.171.70.54.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025020601 1800 900 604800 86400

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 04:43:17 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 54.70.171.116.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 54.70.171.116.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.198.5.79 attackbotsspam
SSH brute-force: detected 7 distinct usernames within a 24-hour window.
2019-12-03 07:47:45
139.59.61.134 attackspam
Dec  2 20:45:39 XXX sshd[11733]: Invalid user kilsaas from 139.59.61.134 port 54401
2019-12-03 08:00:29
114.221.13.110 attackspambots
Dec  3 03:05:10 server sshd\[21584\]: Invalid user alejoa from 114.221.13.110
Dec  3 03:05:10 server sshd\[21584\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.221.13.110 
Dec  3 03:05:12 server sshd\[21584\]: Failed password for invalid user alejoa from 114.221.13.110 port 3532 ssh2
Dec  3 03:18:38 server sshd\[25486\]: Invalid user clerissa from 114.221.13.110
Dec  3 03:18:38 server sshd\[25486\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.221.13.110 
...
2019-12-03 08:23:35
13.56.223.168 attackspambots
Brute forcing RDP port 3389
2019-12-03 08:11:27
200.89.178.164 attackbots
Dec  2 23:56:54 zeus sshd[15057]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.89.178.164 
Dec  2 23:56:55 zeus sshd[15057]: Failed password for invalid user ubuntu from 200.89.178.164 port 58550 ssh2
Dec  3 00:03:41 zeus sshd[15338]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.89.178.164 
Dec  3 00:03:43 zeus sshd[15338]: Failed password for invalid user qdemo from 200.89.178.164 port 42814 ssh2
2019-12-03 08:09:57
106.12.114.26 attackbotsspam
Dec  2 22:34:27 xeon sshd[16833]: Failed password for invalid user yosizaki from 106.12.114.26 port 50296 ssh2
2019-12-03 08:17:54
121.201.4.14 attackspam
RDP Brute-Force (Grieskirchen RZ2)
2019-12-03 08:03:29
182.61.27.149 attackspam
Dec  3 01:07:40 microserver sshd[2099]: Invalid user svr from 182.61.27.149 port 35610
Dec  3 01:07:40 microserver sshd[2099]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.27.149
Dec  3 01:07:42 microserver sshd[2099]: Failed password for invalid user svr from 182.61.27.149 port 35610 ssh2
Dec  3 01:14:06 microserver sshd[2932]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.27.149  user=mysql
Dec  3 01:14:08 microserver sshd[2932]: Failed password for mysql from 182.61.27.149 port 46620 ssh2
Dec  3 01:26:38 microserver sshd[5020]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.27.149  user=root
Dec  3 01:26:40 microserver sshd[5020]: Failed password for root from 182.61.27.149 port 40448 ssh2
Dec  3 01:32:54 microserver sshd[5817]: Invalid user xiaoguang from 182.61.27.149 port 51458
Dec  3 01:32:54 microserver sshd[5817]: pam_unix(sshd:auth): authentication failur
2019-12-03 08:20:07
62.162.103.206 attack
Wordpress Attacks [Scanning for wp-login.php] @ 2019-12-02 23:12:40
2019-12-03 07:58:46
190.116.49.2 attackbots
Brute-force attempt banned
2019-12-03 07:47:06
159.89.175.48 attack
Dec  3 00:27:15 [host] sshd[27669]: Invalid user ident from 159.89.175.48
Dec  3 00:27:15 [host] sshd[27669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.175.48
Dec  3 00:27:17 [host] sshd[27669]: Failed password for invalid user ident from 159.89.175.48 port 57898 ssh2
2019-12-03 08:09:17
140.143.130.52 attackspambots
Dec  2 23:43:00 pi sshd\[22719\]: Failed password for invalid user zp from 140.143.130.52 port 52468 ssh2
Dec  2 23:50:26 pi sshd\[23142\]: Invalid user balmont from 140.143.130.52 port 55472
Dec  2 23:50:26 pi sshd\[23142\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.130.52
Dec  2 23:50:28 pi sshd\[23142\]: Failed password for invalid user balmont from 140.143.130.52 port 55472 ssh2
Dec  3 00:04:38 pi sshd\[23891\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.130.52  user=www-data
...
2019-12-03 08:11:50
13.69.31.111 attackbotsspam
RDP Bruteforce
2019-12-03 07:51:35
185.153.197.162 attackspambots
12/02/2019-18:33:00.449624 185.153.197.162 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-12-03 07:55:09
95.14.156.128 attackbots
Automatic report - Port Scan Attack
2019-12-03 08:01:29

Recently Reported IPs

34.194.217.137 23.66.95.48 237.138.218.220 25.210.101.146
206.78.31.55 131.22.179.156 71.17.174.238 164.14.136.242
97.95.141.63 191.24.151.78 70.134.214.79 87.228.76.81
231.254.97.212 49.147.124.149 158.123.226.197 19.193.206.202
19.141.254.239 123.90.64.35 150.158.130.114 193.6.32.98