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

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:
IP Type Details Datetime
114.104.131.108 attack
Unauthorized connection attempt detected from IP address 114.104.131.108 to port 6656 [T]
2020-01-30 16:30:54
114.104.131.176 attack
Unauthorized connection attempt detected from IP address 114.104.131.176 to port 6656 [T]
2020-01-29 17:03:14
114.104.131.243 attackbotsspam
badbot
2019-11-23 03:52:53
114.104.131.46 attack
badbot
2019-11-20 16:31:53
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.104.131.121
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20242
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;114.104.131.121.		IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 14:33:22 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 121.131.104.114.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 121.131.104.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
36.67.63.9 attackspam
(sshd) Failed SSH login from 36.67.63.9 (ID/Indonesia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 15 23:13:57 amsweb01 sshd[24632]: Invalid user tests from 36.67.63.9 port 34120
Apr 15 23:13:59 amsweb01 sshd[24632]: Failed password for invalid user tests from 36.67.63.9 port 34120 ssh2
Apr 15 23:29:56 amsweb01 sshd[26760]: Invalid user zeyu from 36.67.63.9 port 36742
Apr 15 23:29:58 amsweb01 sshd[26760]: Failed password for invalid user zeyu from 36.67.63.9 port 36742 ssh2
Apr 15 23:34:32 amsweb01 sshd[27282]: Invalid user cdv from 36.67.63.9 port 39882
2020-04-16 07:15:35
156.220.10.127 attack
2020-04-15T13:23:34.841064-07:00 suse-nuc sshd[8371]: Invalid user admin from 156.220.10.127 port 35689
...
2020-04-16 07:13:11
138.197.66.68 attack
Apr 15 07:41:41: Invalid user mcUser from 138.197.66.68 port 60586
2020-04-16 07:21:57
194.61.27.249 attackspam
04/15/2020-19:09:53.803260 194.61.27.249 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-16 07:16:37
122.192.255.228 attackspambots
Invalid user george from 122.192.255.228 port 11250
2020-04-16 07:05:09
139.59.67.82 attackspam
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-04-16 07:32:42
222.186.15.114 attackspam
Apr 16 01:13:51 *host* sshd\[28325\]: User *user* from 222.186.15.114 not allowed because none of user's groups are listed in AllowGroups
2020-04-16 07:17:08
106.12.182.1 attackspam
Invalid user guest from 106.12.182.1 port 37328
2020-04-16 07:19:25
49.234.16.16 attackspam
04/15/2020-16:56:02.342541 49.234.16.16 Protocol: 6 ET SCAN Potential SSH Scan
2020-04-16 07:20:19
142.93.195.15 attackspam
Invalid user yd from 142.93.195.15 port 37296
2020-04-16 07:08:03
92.118.38.83 attackbots
'IP reached maximum auth failures'
2020-04-16 07:24:45
51.254.220.61 attackbots
Invalid user vcr from 51.254.220.61 port 59537
2020-04-16 07:29:25
59.173.12.106 attackspambots
failed_logins
2020-04-16 07:10:41
209.17.96.130 attackspambots
Brute force attack stopped by firewall
2020-04-16 07:26:51
209.17.96.242 attackspambots
port scan and connect, tcp 22 (ssh)
2020-04-16 07:25:32

Recently Reported IPs

114.104.130.240 114.104.131.138 114.104.131.141 113.250.157.142
114.104.131.125 114.104.131.182 114.104.131.192 114.104.131.127
114.104.131.163 114.104.131.25 114.104.131.201 114.104.131.194
114.104.131.43 114.104.131.29 114.104.131.232 113.250.157.15
114.104.131.69 114.104.131.56 114.104.131.32 114.104.131.52