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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 131.161.104.2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60424
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;131.161.104.2.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 05:29:25 CST 2022
;; MSG SIZE  rcvd: 106
Host info
2.104.161.131.in-addr.arpa domain name pointer 131-161-104-2.rev.netcorporativa.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
2.104.161.131.in-addr.arpa	name = 131-161-104-2.rev.netcorporativa.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
183.100.185.92 attack
firewall-block, port(s): 2323/tcp
2019-07-09 18:04:10
67.205.177.0 attackspambots
ssh failed login
2019-07-09 18:20:47
192.144.159.186 attack
schuetzenmusikanten.de 192.144.159.186 \[09/Jul/2019:09:47:14 +0200\] "POST /wp-login.php HTTP/1.1" 200 5684 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
schuetzenmusikanten.de 192.144.159.186 \[09/Jul/2019:09:47:17 +0200\] "POST /wp-login.php HTTP/1.1" 200 5650 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
schuetzenmusikanten.de 192.144.159.186 \[09/Jul/2019:09:47:19 +0200\] "POST /wp-login.php HTTP/1.1" 200 5641 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-07-09 18:22:30
119.187.151.218 attackbots
2019-07-09T17:12:43.215637enmeeting.mahidol.ac.th sshd\[19738\]: Invalid user nologin from 119.187.151.218 port 56622
2019-07-09T17:12:43.229009enmeeting.mahidol.ac.th sshd\[19738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.187.151.218
2019-07-09T17:12:45.250156enmeeting.mahidol.ac.th sshd\[19738\]: Failed password for invalid user nologin from 119.187.151.218 port 56622 ssh2
...
2019-07-09 18:45:59
42.202.33.241 attackbotsspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.202.33.241  user=nagios
Failed password for nagios from 42.202.33.241 port 45422 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.202.33.241  user=root
Failed password for root from 42.202.33.241 port 58543 ssh2
Invalid user ho from 42.202.33.241 port 38426
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.202.33.241
2019-07-09 18:37:12
39.48.71.224 attackspambots
port scan and connect, tcp 22 (ssh)
2019-07-09 18:43:08
91.191.223.207 attack
Jul  8 18:43:19 cac1d2 postfix/smtpd\[32048\]: warning: unknown\[91.191.223.207\]: SASL LOGIN authentication failed: authentication failure
Jul  8 19:31:35 cac1d2 postfix/smtpd\[32227\]: warning: unknown\[91.191.223.207\]: SASL LOGIN authentication failed: authentication failure
Jul  8 20:19:25 cac1d2 postfix/smtpd\[9165\]: warning: unknown\[91.191.223.207\]: SASL LOGIN authentication failed: authentication failure
...
2019-07-09 18:17:29
201.99.120.13 attackbotsspam
Jul  9 09:16:05 ip-172-31-62-245 sshd\[32563\]: Failed password for root from 201.99.120.13 port 21313 ssh2\
Jul  9 09:22:59 ip-172-31-62-245 sshd\[32587\]: Invalid user webs from 201.99.120.13\
Jul  9 09:23:01 ip-172-31-62-245 sshd\[32587\]: Failed password for invalid user webs from 201.99.120.13 port 11537 ssh2\
Jul  9 09:23:57 ip-172-31-62-245 sshd\[32592\]: Invalid user vnc from 201.99.120.13\
Jul  9 09:23:59 ip-172-31-62-245 sshd\[32592\]: Failed password for invalid user vnc from 201.99.120.13 port 14201 ssh2\
2019-07-09 18:41:08
18.191.133.7 attack
Received: from ec2-18-191-133-7.us-east-2.compute.amazonaws.com ([18.191.133.7] helo=vivo.com.br)
2019-07-09 18:20:10
52.233.164.94 attackspambots
LGS,WP GET /wordpress8/wp-login.php
2019-07-09 17:56:20
54.36.150.100 attack
Automatic report - Web App Attack
2019-07-09 18:13:48
132.232.31.109 attackspam
132.232.31.109 - - [09/Jul/2019:05:18:45 +0200] "POST /Appa375c6d9.php HTTP/1.1" 301 185 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36"
132.232.31.109 - - [09/Jul/2019:05:18:46 +0200] "GET /webdav/ HTTP/1.1" 301 185 "-" "Mozilla/5.0"
...
2019-07-09 18:28:12
121.101.133.220 attack
2019-07-09T05:17:36.0104241240 sshd\[24116\]: Invalid user user1 from 121.101.133.220 port 59340
2019-07-09T05:17:36.2106101240 sshd\[24116\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.101.133.220
2019-07-09T05:17:37.6018531240 sshd\[24116\]: Failed password for invalid user user1 from 121.101.133.220 port 59340 ssh2
...
2019-07-09 18:48:20
177.72.131.95 attackbots
smtp auth brute force
2019-07-09 17:57:28
86.102.122.178 attackspambots
Brute force attempt
2019-07-09 18:35:23

Recently Reported IPs

131.161.104.97 131.161.104.66 131.161.104.34 131.161.104.6
131.161.104.41 118.172.231.254 118.172.231.39 131.161.119.105
131.161.107.14 131.161.119.109 131.161.105.77 131.161.107.34
131.161.107.13 131.161.107.105 131.161.107.60 131.161.107.185
131.161.108.209 131.161.119.115 131.161.119.119 118.172.231.43