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: Changsha

Region: Hunan

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 <<>> 106.34.81.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11487
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;106.34.81.164.			IN	A

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

;; Query time: 83 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jun 15 07:18:20 CST 2020
;; MSG SIZE  rcvd: 117
Host info
;; connection timed out; no servers could be reached
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 164.81.34.106.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
193.70.0.42 attackspambots
pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.0.42 
Failed password for invalid user khs from 193.70.0.42 port 53094 ssh2
pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.0.42
2020-01-25 17:36:51
125.224.106.125 attackbotsspam
Unauthorized connection attempt detected from IP address 125.224.106.125 to port 23 [J]
2020-01-25 17:31:00
112.112.114.133 attackbots
Unauthorized connection attempt detected from IP address 112.112.114.133 to port 5555 [J]
2020-01-25 17:45:22
220.135.108.62 attackspambots
Unauthorized connection attempt detected from IP address 220.135.108.62 to port 23 [J]
2020-01-25 18:00:03
124.156.54.111 attack
Unauthorized connection attempt detected from IP address 124.156.54.111 to port 6060 [J]
2020-01-25 17:44:13
49.51.12.179 attackspam
Unauthorized connection attempt detected from IP address 49.51.12.179 to port 7788 [J]
2020-01-25 17:53:55
150.109.229.166 attackbots
Unauthorized connection attempt detected from IP address 150.109.229.166 to port 7071 [J]
2020-01-25 17:43:08
45.80.65.83 attackbotsspam
Unauthorized connection attempt detected from IP address 45.80.65.83 to port 2220 [J]
2020-01-25 17:27:36
24.234.48.230 attackspambots
Unauthorized connection attempt detected from IP address 24.234.48.230 to port 23 [J]
2020-01-25 17:57:25
139.155.22.165 attackspam
Unauthorized connection attempt detected from IP address 139.155.22.165 to port 2220 [J]
2020-01-25 17:30:26
210.176.62.116 attackbotsspam
Unauthorized connection attempt detected from IP address 210.176.62.116 to port 2220 [J]
2020-01-25 17:35:38
27.62.138.32 attack
firewall-block, port(s): 1433/tcp
2020-01-25 17:26:49
171.1.233.225 attackbotsspam
Automatic report - SSH Brute-Force Attack
2020-01-25 17:28:09
62.140.224.186 attackbotsspam
Unauthorized connection attempt detected from IP address 62.140.224.186 to port 8080 [J]
2020-01-25 17:52:26
14.162.92.20 attackbots
Unauthorized connection attempt detected from IP address 14.162.92.20 to port 88 [J]
2020-01-25 17:57:56

Recently Reported IPs

72.178.225.104 211.131.176.41 220.63.91.121 158.222.208.86
10.185.81.159 180.190.225.13 147.50.47.227 112.236.98.201
151.22.190.41 52.9.182.154 70.244.39.91 141.222.13.138
178.26.225.6 192.241.204.14 72.176.218.85 212.226.249.132
99.238.67.140 18.130.82.97 36.99.218.124 177.177.121.37