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

;; QUESTION SECTION:
;106.14.45.59.			IN	A

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

;; Query time: 26 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 14:32:58 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 59.45.14.106.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 59.45.14.106.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
95.13.74.199 attack
Unauthorized connection attempt detected from IP address 95.13.74.199 to port 4567 [J]
2020-01-19 05:11:08
171.240.144.226 attackbotsspam
Unauthorized connection attempt detected from IP address 171.240.144.226 to port 88 [J]
2020-01-19 05:04:51
129.28.153.112 attackbots
Jan 18 22:26:54 server sshd\[684\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.153.112  user=root
Jan 18 22:26:55 server sshd\[684\]: Failed password for root from 129.28.153.112 port 42750 ssh2
Jan 18 23:55:09 server sshd\[22754\]: Invalid user fctrserver from 129.28.153.112
Jan 18 23:55:09 server sshd\[22754\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.153.112 
Jan 18 23:55:11 server sshd\[22754\]: Failed password for invalid user fctrserver from 129.28.153.112 port 56626 ssh2
...
2020-01-19 05:05:42
61.8.69.98 attack
Unauthorized connection attempt detected from IP address 61.8.69.98 to port 2220 [J]
2020-01-19 05:14:45
113.172.143.88 attackspam
Invalid user admin from 113.172.143.88 port 56431
2020-01-19 04:43:40
187.190.48.55 attackbotsspam
Unauthorized connection attempt detected from IP address 187.190.48.55 to port 8000 [J]
2020-01-19 05:02:30
77.70.71.205 attackbots
Unauthorized connection attempt detected from IP address 77.70.71.205 to port 2220 [J]
2020-01-19 04:53:17
54.39.50.204 attack
Unauthorized connection attempt detected from IP address 54.39.50.204 to port 2220 [J]
2020-01-19 05:15:29
62.234.157.189 attack
Unauthorized connection attempt detected from IP address 62.234.157.189 to port 80 [J]
2020-01-19 05:14:21
124.112.114.111 attackbotsspam
Unauthorized connection attempt detected from IP address 124.112.114.111 to port 1433 [J]
2020-01-19 05:06:27
211.157.179.168 attackbots
Unauthorized connection attempt detected from IP address 211.157.179.168 to port 1433 [J]
2020-01-19 05:00:52
95.90.154.148 attackbotsspam
Invalid user vbox from 95.90.154.148 port 51533
2020-01-19 04:48:50
217.24.253.142 attack
Unauthorized connection attempt detected from IP address 217.24.253.142 to port 80 [J]
2020-01-19 05:20:01
94.232.6.101 attackspambots
Unauthorized connection attempt detected from IP address 94.232.6.101 to port 83 [J]
2020-01-19 05:11:37
81.214.68.227 attackbots
Unauthorized connection attempt detected from IP address 81.214.68.227 to port 23 [J]
2020-01-19 05:13:24

Recently Reported IPs

106.14.45.174 106.14.95.42 106.14.95.57 106.14.96.104
106.14.96.152 106.14.96.190 106.14.96.20 106.14.96.27
106.14.97.121 106.14.96.74 106.14.97.134 106.14.97.155
106.14.97.13 106.14.97.127 106.14.97.161 106.14.96.37
106.14.97.17 106.14.97.163 106.14.97.43 106.14.98.216