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

;; QUESTION SECTION:
;112.66.214.140.			IN	A

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

;; Query time: 89 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 05:51:20 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 140.214.66.112.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 140.214.66.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
81.169.145.98 attack
SSH login attempts.
2020-02-17 17:56:17
195.4.92.218 attack
SSH login attempts.
2020-02-17 18:11:05
196.218.157.102 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 18:10:42
104.31.66.63 attackspam
SSH login attempts.
2020-02-17 17:36:55
80.12.70.19 attack
SSH login attempts.
2020-02-17 17:47:19
129.28.166.212 attackbots
2020-02-17T05:56:49.045191  sshd[24978]: Invalid user abc123 from 129.28.166.212 port 39418
2020-02-17T05:56:49.060186  sshd[24978]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.166.212
2020-02-17T05:56:49.045191  sshd[24978]: Invalid user abc123 from 129.28.166.212 port 39418
2020-02-17T05:56:50.684185  sshd[24978]: Failed password for invalid user abc123 from 129.28.166.212 port 39418 ssh2
...
2020-02-17 17:32:03
178.176.30.211 attackbotsspam
Feb 17 05:41:46 ovpn sshd\[30238\]: Invalid user operador from 178.176.30.211
Feb 17 05:41:46 ovpn sshd\[30238\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.176.30.211
Feb 17 05:41:47 ovpn sshd\[30238\]: Failed password for invalid user operador from 178.176.30.211 port 35380 ssh2
Feb 17 05:56:32 ovpn sshd\[1559\]: Invalid user sun from 178.176.30.211
Feb 17 05:56:32 ovpn sshd\[1559\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.176.30.211
2020-02-17 17:53:44
129.211.124.29 attackbotsspam
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-02-17 17:38:08
5.188.86.212 attackbotsspam
SSH login attempts.
2020-02-17 17:34:23
216.70.64.58 attack
SSH login attempts.
2020-02-17 17:36:20
49.234.96.24 attackbots
Feb 17 04:56:32 ws26vmsma01 sshd[203527]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.96.24
Feb 17 04:56:34 ws26vmsma01 sshd[203527]: Failed password for invalid user browser from 49.234.96.24 port 46756 ssh2
...
2020-02-17 17:50:53
104.47.32.33 attackspambots
SSH login attempts.
2020-02-17 18:05:54
1.7.7.1 attackspam
SSH login attempts.
2020-02-17 17:59:18
181.189.135.10 attack
trying to hack server through RDP
2020-02-17 17:36:13
223.207.241.252 attack
20/2/16@23:56:21: FAIL: Alarm-Network address from=223.207.241.252
...
2020-02-17 18:08:22

Recently Reported IPs

112.66.212.226 112.66.215.77 112.66.240.126 112.66.210.46
112.66.220.158 112.66.240.160 112.66.241.17 112.66.241.22
112.66.242.44 112.66.243.132 112.66.244.123 112.66.244.70
112.66.245.113 112.66.245.134 112.66.248.136 112.66.249.18
112.66.249.217 112.66.249.151 112.66.249.39 112.66.249.58