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: Republic of China (ROC)

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

;; QUESTION SECTION:
;114.34.66.190.			IN	A

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

;; Query time: 187 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 11 23:32:35 CST 2022
;; MSG SIZE  rcvd: 106
Host info
190.66.34.114.in-addr.arpa domain name pointer 114-34-66-190.hinet-ip.hinet.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
190.66.34.114.in-addr.arpa	name = 114-34-66-190.hinet-ip.hinet.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
146.185.142.70 attackspambots
masscan/1.0 (https://github.com/robertdavidgraham/masscan)
2019-12-15 20:57:23
209.17.97.18 attackbots
209.17.97.18 was recorded 13 times by 9 hosts attempting to connect to the following ports: 3052,8080,6002,554,53,50070,20,1025,27017,2483,5443,1434. Incident counter (4h, 24h, all-time): 13, 53, 1647
2019-12-15 20:40:39
192.171.85.3 attackbotsspam
(From minton.garland51@hotmail.com) Hey,

I heard about SocialAdr from a friend of mine but was hesitant at first, because it sounded too good to be true.  She told me, "All you have to do is enter your web page details and other members promote your URLs to their social media profiles automatically.  It literally takes 5 minutes to get setup."

So I figured, "What the heck!", I may as well give it a try.

I signed up for the 'Free' account and found the Setup Wizard super easy to use.  With the 'Free' account you have to setup all your own social media accounts (only once though) in order to get started.  Next, I shared 5 other members' links, which was as simple as clicking a single button.  I had to do this first in order to earn "credits" which can then be spent when other members share my links.  Then I added a couple of my own web pages and a short while later started receiving notification that they had been submitted to a list of social media sites.

Wow.  And this was just with the 'Free' acc
2019-12-15 20:56:59
119.10.114.5 attackspam
sshd jail - ssh hack attempt
2019-12-15 20:55:59
78.27.172.65 attackbotsspam
2019-12-15T13:03:53.802287scmdmz1 sshd\[17718\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=unnum-78-27-172-65.domashka.kiev.ua  user=root
2019-12-15T13:03:55.754059scmdmz1 sshd\[17718\]: Failed password for root from 78.27.172.65 port 40158 ssh2
2019-12-15T13:09:42.995499scmdmz1 sshd\[18214\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=unnum-78-27-172-65.domashka.kiev.ua  user=root
...
2019-12-15 20:20:18
185.156.73.42 attackbotsspam
ET DROP Dshield Block Listed Source group 1 - port: 12943 proto: TCP cat: Misc Attack
2019-12-15 20:23:16
134.236.86.200 attackspambots
Unauthorised access (Dec 15) SRC=134.236.86.200 LEN=52 PREC=0x20 TTL=115 ID=18040 DF TCP DPT=445 WINDOW=8192 SYN
2019-12-15 20:34:02
114.141.191.238 attack
Dec 15 12:09:53 sd-53420 sshd\[5520\]: User www-data from 114.141.191.238 not allowed because none of user's groups are listed in AllowGroups
Dec 15 12:09:53 sd-53420 sshd\[5520\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.141.191.238  user=www-data
Dec 15 12:09:56 sd-53420 sshd\[5520\]: Failed password for invalid user www-data from 114.141.191.238 port 48405 ssh2
Dec 15 12:16:23 sd-53420 sshd\[7369\]: User root from 114.141.191.238 not allowed because none of user's groups are listed in AllowGroups
Dec 15 12:16:23 sd-53420 sshd\[7369\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.141.191.238  user=root
...
2019-12-15 20:27:14
104.168.34.152 attackspam
TCP Port Scanning
2019-12-15 20:56:21
59.45.97.190 attackbotsspam
Dec 15 13:23:50 lcl-usvr-01 sshd[4922]: refused connect from 59.45.97.190 (59.45.97.190)
Dec 15 13:24:43 lcl-usvr-01 sshd[5233]: refused connect from 59.45.97.190 (59.45.97.190)
Dec 15 13:24:43 lcl-usvr-01 sshd[5234]: refused connect from 59.45.97.190 (59.45.97.190)
Dec 15 13:24:43 lcl-usvr-01 sshd[5235]: refused connect from 59.45.97.190 (59.45.97.190)
2019-12-15 20:49:48
122.51.83.37 attackbots
Dec 15 08:50:07 server sshd\[19699\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.83.37  user=root
Dec 15 08:50:09 server sshd\[19699\]: Failed password for root from 122.51.83.37 port 52970 ssh2
Dec 15 09:10:06 server sshd\[25562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.83.37  user=root
Dec 15 09:10:08 server sshd\[25562\]: Failed password for root from 122.51.83.37 port 51566 ssh2
Dec 15 09:24:58 server sshd\[29897\]: Invalid user hkaysoh from 122.51.83.37
Dec 15 09:24:58 server sshd\[29897\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.83.37 
...
2019-12-15 20:42:14
223.220.114.58 attack
Scanning
2019-12-15 20:51:03
51.83.76.203 attackspambots
Dec 15 09:50:18 ws12vmsma01 sshd[32971]: Invalid user manou from 51.83.76.203
Dec 15 09:50:20 ws12vmsma01 sshd[32971]: Failed password for invalid user manou from 51.83.76.203 port 46750 ssh2
Dec 15 09:55:21 ws12vmsma01 sshd[33694]: Invalid user baha from 51.83.76.203
...
2019-12-15 20:14:12
112.21.191.244 attackspambots
Dec 15 12:43:44 loxhost sshd\[23249\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.21.191.244  user=backup
Dec 15 12:43:47 loxhost sshd\[23249\]: Failed password for backup from 112.21.191.244 port 34646 ssh2
Dec 15 12:50:35 loxhost sshd\[23466\]: Invalid user rossy from 112.21.191.244 port 51896
Dec 15 12:50:35 loxhost sshd\[23466\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.21.191.244
Dec 15 12:50:37 loxhost sshd\[23466\]: Failed password for invalid user rossy from 112.21.191.244 port 51896 ssh2
...
2019-12-15 20:51:50
128.199.224.215 attack
Dec 14 23:00:46 web1 sshd\[28962\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.224.215  user=games
Dec 14 23:00:48 web1 sshd\[28962\]: Failed password for games from 128.199.224.215 port 57014 ssh2
Dec 14 23:07:31 web1 sshd\[29928\]: Invalid user fukuda from 128.199.224.215
Dec 14 23:07:31 web1 sshd\[29928\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.224.215
Dec 14 23:07:33 web1 sshd\[29928\]: Failed password for invalid user fukuda from 128.199.224.215 port 34744 ssh2
2019-12-15 20:54:26

Recently Reported IPs

78.188.170.106 117.251.85.118 171.116.232.114 119.36.47.203
43.142.34.186 223.10.52.231 124.221.72.112 125.27.42.85
27.220.91.1 175.213.185.191 168.90.253.49 23.94.213.211
31.40.136.187 103.165.156.157 103.241.205.77 190.99.181.18
95.111.200.215 82.48.249.129 117.254.37.223 180.103.163.214