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

;; QUESTION SECTION:
;114.187.50.131.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 03:38:51 CST 2025
;; MSG SIZE  rcvd: 107
Host info
131.50.187.114.in-addr.arpa domain name pointer i114-187-50-131.s99.a049.ap.plala.or.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
131.50.187.114.in-addr.arpa	name = i114-187-50-131.s99.a049.ap.plala.or.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.30.76 attackbotsspam
Unauthorized connection attempt detected from IP address 222.186.30.76 to port 22 [J]
2020-01-08 13:10:55
120.131.3.91 attackbots
Jan  8 05:52:31 legacy sshd[27036]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.131.3.91
Jan  8 05:52:33 legacy sshd[27036]: Failed password for invalid user ubuntu from 120.131.3.91 port 27058 ssh2
Jan  8 05:57:05 legacy sshd[27323]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.131.3.91
...
2020-01-08 13:03:20
133.130.117.173 attackbots
Too many connections or unauthorized access detected from Arctic banned ip
2020-01-08 09:06:00
35.223.236.180 attackbotsspam
WordPress brute force
2020-01-08 09:29:11
37.144.138.108 attackbotsspam
Automatic report - Port Scan Attack
2020-01-08 13:16:07
200.2.29.17 attackspambots
Unauthorized connection attempt from IP address 200.2.29.17 on Port 445(SMB)
2020-01-08 09:25:47
40.101.84.2 attack
DoS attack: ACK Scan
2020-01-08 09:13:27
125.165.10.39 attackbots
Unauthorized connection attempt from IP address 125.165.10.39 on Port 445(SMB)
2020-01-08 09:19:25
200.123.0.114 attackbotsspam
Unauthorized connection attempt from IP address 200.123.0.114 on Port 445(SMB)
2020-01-08 09:21:36
111.67.197.14 attack
Unauthorized connection attempt detected from IP address 111.67.197.14 to port 2220 [J]
2020-01-08 09:11:25
196.188.243.246 attackspambots
Unauthorized connection attempt from IP address 196.188.243.246 on Port 445(SMB)
2020-01-08 09:13:55
51.38.71.174 attackbotsspam
Unauthorized connection attempt detected from IP address 51.38.71.174 to port 2220 [J]
2020-01-08 09:07:42
104.248.227.130 attackbotsspam
01/08/2020-00:09:18.535621 104.248.227.130 Protocol: 6 ET SCAN Potential SSH Scan
2020-01-08 13:10:30
109.70.100.29 attackspambots
Automatic report - XMLRPC Attack
2020-01-08 09:16:56
91.234.217.189 attackbots
WordPress brute force
2020-01-08 09:20:30

Recently Reported IPs

52.182.101.175 206.136.67.231 211.214.20.120 91.62.153.152
132.39.39.15 244.152.110.71 21.213.238.13 124.195.60.167
212.102.118.186 192.117.118.42 179.58.76.110 207.129.179.228
20.136.164.156 82.154.235.50 227.217.162.233 162.104.5.75
223.82.19.106 51.171.54.205 141.81.154.224 245.244.146.187