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

Region: Tokyo

Country: Japan

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

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

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 22 04:27:19 CST 2020
;; MSG SIZE  rcvd: 117
Host info
1.196.164.114.in-addr.arpa domain name pointer p4838001-ipngn27201marunouchi.tokyo.ocn.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
1.196.164.114.in-addr.arpa	name = p4838001-ipngn27201marunouchi.tokyo.ocn.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
202.126.208.122 attackspambots
2019-12-22T05:49:46.879440  sshd[2996]: Invalid user partner from 202.126.208.122 port 53483
2019-12-22T05:49:46.894791  sshd[2996]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.126.208.122
2019-12-22T05:49:46.879440  sshd[2996]: Invalid user partner from 202.126.208.122 port 53483
2019-12-22T05:49:48.846742  sshd[2996]: Failed password for invalid user partner from 202.126.208.122 port 53483 ssh2
2019-12-22T05:55:14.885005  sshd[3085]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.126.208.122  user=root
2019-12-22T05:55:16.866803  sshd[3085]: Failed password for root from 202.126.208.122 port 54144 ssh2
...
2019-12-22 13:24:15
218.92.0.171 attack
2019-12-22T05:24:49.484609abusebot-4.cloudsearch.cf sshd[9008]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.171  user=root
2019-12-22T05:24:51.475872abusebot-4.cloudsearch.cf sshd[9008]: Failed password for root from 218.92.0.171 port 55689 ssh2
2019-12-22T05:24:54.435580abusebot-4.cloudsearch.cf sshd[9008]: Failed password for root from 218.92.0.171 port 55689 ssh2
2019-12-22T05:24:49.484609abusebot-4.cloudsearch.cf sshd[9008]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.171  user=root
2019-12-22T05:24:51.475872abusebot-4.cloudsearch.cf sshd[9008]: Failed password for root from 218.92.0.171 port 55689 ssh2
2019-12-22T05:24:54.435580abusebot-4.cloudsearch.cf sshd[9008]: Failed password for root from 218.92.0.171 port 55689 ssh2
2019-12-22T05:24:49.484609abusebot-4.cloudsearch.cf sshd[9008]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.
...
2019-12-22 13:27:31
222.186.175.147 attack
Dec 22 06:12:33 icinga sshd[4625]: Failed password for root from 222.186.175.147 port 58376 ssh2
Dec 22 06:12:46 icinga sshd[4625]: error: maximum authentication attempts exceeded for root from 222.186.175.147 port 58376 ssh2 [preauth]
...
2019-12-22 13:16:45
41.162.104.98 attackspam
1576990531 - 12/22/2019 05:55:31 Host: 41.162.104.98/41.162.104.98 Port: 445 TCP Blocked
2019-12-22 13:11:20
59.51.65.17 attack
SSH invalid-user multiple login try
2019-12-22 13:05:20
129.211.17.22 attackspambots
Dec 21 23:55:36 TORMINT sshd\[943\]: Invalid user 44444444 from 129.211.17.22
Dec 21 23:55:36 TORMINT sshd\[943\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.17.22
Dec 21 23:55:38 TORMINT sshd\[943\]: Failed password for invalid user 44444444 from 129.211.17.22 port 60038 ssh2
...
2019-12-22 13:02:48
74.63.226.142 attackbots
Dec 21 18:49:47 web1 sshd\[29931\]: Invalid user crans from 74.63.226.142
Dec 21 18:49:47 web1 sshd\[29931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.63.226.142
Dec 21 18:49:49 web1 sshd\[29931\]: Failed password for invalid user crans from 74.63.226.142 port 57536 ssh2
Dec 21 18:55:30 web1 sshd\[30479\]: Invalid user pellan from 74.63.226.142
Dec 21 18:55:30 web1 sshd\[30479\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.63.226.142
2019-12-22 13:10:49
80.211.231.224 attackbotsspam
Dec 22 07:55:18 hosting sshd[13149]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.231.224  user=games
Dec 22 07:55:20 hosting sshd[13149]: Failed password for games from 80.211.231.224 port 39872 ssh2
...
2019-12-22 13:21:19
106.111.210.51 attack
Brute force SMTP login attempts.
2019-12-22 09:31:17
136.43.32.84 attackspam
404 NOT FOUND
2019-12-22 13:28:30
185.215.63.197 attackbotsspam
Honeypot attack, port: 23, PTR: E4186B01C4FD.mldns.ru.
2019-12-22 13:23:12
201.210.43.223 attackbots
1576990536 - 12/22/2019 05:55:36 Host: 201.210.43.223/201.210.43.223 Port: 445 TCP Blocked
2019-12-22 13:04:42
171.103.141.50 attack
Dec 21 23:56:22 ns3042688 courier-imapd: LOGIN FAILED, method=PLAIN, ip=\[::ffff:171.103.141.50\]
...
2019-12-22 09:30:58
190.7.146.165 attackspambots
Brute-force attempt banned
2019-12-22 13:12:29
94.69.11.218 attack
Unauthorized connection attempt detected from IP address 94.69.11.218 to port 445
2019-12-22 09:24:47

Recently Reported IPs

52.160.6.98 62.72.217.164 89.244.90.90 66.26.228.117
218.234.50.16 114.32.36.74 84.236.174.194 54.160.16.150
109.157.88.61 204.45.13.115 46.122.120.56 125.29.56.218
46.119.129.193 49.169.13.236 75.234.96.179 216.24.85.247
23.94.167.101 124.228.180.230 156.246.218.145 5.143.44.217