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

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Sun Jun 30 20:56:14 CST 2019
;; MSG SIZE  rcvd: 118
Host info
Host 113.106.159.14.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

** server can't find 113.106.159.14.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
193.112.125.249 attackbots
Invalid user t from 193.112.125.249 port 55596
2020-04-22 02:04:51
202.186.38.188 attack
prod6
...
2020-04-22 02:01:18
140.143.167.2 attackbotsspam
"fail2ban match"
2020-04-22 02:20:22
132.232.109.120 attack
Invalid user qe from 132.232.109.120 port 36136
2020-04-22 02:21:04
213.234.252.110 attackbots
SSH Brute-Forcing (server1)
2020-04-22 01:57:16
180.107.123.166 attackbotsspam
2020-04-21T19:18:45.974036  sshd[30051]: Invalid user test3 from 180.107.123.166 port 27783
2020-04-21T19:18:45.988363  sshd[30051]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.107.123.166
2020-04-21T19:18:45.974036  sshd[30051]: Invalid user test3 from 180.107.123.166 port 27783
2020-04-21T19:18:47.988134  sshd[30051]: Failed password for invalid user test3 from 180.107.123.166 port 27783 ssh2
...
2020-04-22 02:10:24
34.92.237.74 attackbotsspam
(sshd) Failed SSH login from 34.92.237.74 (US/United States/74.237.92.34.bc.googleusercontent.com): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 21 18:26:23 ubnt-55d23 sshd[5242]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.92.237.74  user=root
Apr 21 18:26:25 ubnt-55d23 sshd[5242]: Failed password for root from 34.92.237.74 port 36120 ssh2
2020-04-22 01:47:21
190.144.67.42 attack
Invalid user biz from 190.144.67.42 port 58434
2020-04-22 02:06:12
209.141.55.11 attackbotsspam
Apr 21 16:39:22 nextcloud sshd\[16606\]: Invalid user oracle from 209.141.55.11
Apr 21 16:39:22 nextcloud sshd\[16603\]: Invalid user postgres from 209.141.55.11
Apr 21 16:39:22 nextcloud sshd\[16601\]: Invalid user test from 209.141.55.11
Apr 21 16:39:22 nextcloud sshd\[16602\]: Invalid user java from 209.141.55.11
Apr 21 16:39:22 nextcloud sshd\[16599\]: Invalid user user from 209.141.55.11
Apr 21 16:39:22 nextcloud sshd\[16605\]: Invalid user ec2-user from 209.141.55.11
Apr 21 16:39:22 nextcloud sshd\[16608\]: Invalid user vagrant from 209.141.55.11
2020-04-22 01:59:16
142.11.195.197 attack
SSH login attempts.
2020-04-22 02:19:52
212.64.71.132 attack
Invalid user admin from 212.64.71.132 port 47920
2020-04-22 01:58:32
201.245.190.106 attackspambots
Invalid user oradev from 201.245.190.106 port 2183
2020-04-22 02:02:49
170.84.209.222 attack
Invalid user do from 170.84.209.222 port 60946
2020-04-22 02:16:24
203.63.75.248 attackbotsspam
Invalid user ubuntu2 from 203.63.75.248 port 38564
2020-04-22 02:00:29
189.190.39.56 attackbotsspam
fail2ban
2020-04-22 02:06:41

Recently Reported IPs

143.160.28.15 63.242.166.24 174.75.185.175 157.150.106.56
179.108.245.199 141.255.8.183 93.144.123.103 188.19.176.72
223.240.249.239 122.191.24.209 187.120.130.109 59.115.133.25
85.100.4.157 177.74.182.41 90.145.66.43 177.73.20.189
84.200.92.221 179.185.70.32 177.21.131.29 193.56.29.106