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

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
131.161.87.76 attack
Automatic report - Port Scan Attack
2020-07-10 05:19:55
131.161.84.232 attackspam
Automatic report - Port Scan Attack
2019-11-24 17:29:16
131.161.85.130 attackbots
Automatic report - Port Scan Attack
2019-11-13 20:52:18
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 131.161.8.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25081
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;131.161.8.12.			IN	A

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

;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 15 12:24:38 CST 2022
;; MSG SIZE  rcvd: 105
Host info
12.8.161.131.in-addr.arpa domain name pointer static-131-161-8-12.gptelecomprovedor.net.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.8.161.131.in-addr.arpa	name = static-131-161-8-12.gptelecomprovedor.net.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
172.119.101.33 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-16 21:24:05
139.99.78.208 attackbotsspam
2019-10-16T12:59:00.322136abusebot-5.cloudsearch.cf sshd\[22016\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.78.208  user=root
2019-10-16 21:22:03
179.108.22.154 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-16 21:47:57
5.196.70.107 attack
$f2bV_matches
2019-10-16 21:37:51
185.197.74.200 attackbots
Oct 16 00:23:21 kmh-mb-001 sshd[4167]: Did not receive identification string from 185.197.74.200 port 1718
Oct 16 00:23:22 kmh-mb-001 sshd[4168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.197.74.200  user=r.r
Oct 16 00:23:25 kmh-mb-001 sshd[4168]: Failed password for r.r from 185.197.74.200 port 27376 ssh2
Oct 16 00:23:27 kmh-mb-001 sshd[4170]: Invalid user support from 185.197.74.200 port 6414
Oct 16 00:23:28 kmh-mb-001 sshd[4170]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.197.74.200
Oct 16 00:23:28 kmh-mb-001 sshd[4168]: Connection closed by 185.197.74.200 port 27376 [preauth]
Oct 16 00:23:30 kmh-mb-001 sshd[4170]: Failed password for invalid user support from 185.197.74.200 port 6414 ssh2
Oct 16 00:23:30 kmh-mb-001 sshd[4170]: Connection closed by 185.197.74.200 port 6414 [preauth]
Oct 16 00:23:30 kmh-mb-001 sshd[4172]: Invalid user admin from 185.197.74.200 port 41160........
-------------------------------
2019-10-16 21:37:24
51.254.210.53 attackspam
Automatic report - Banned IP Access
2019-10-16 21:30:21
49.207.140.118 attackbots
Sniffing for wp-login
2019-10-16 21:43:21
100.21.65.16 attackspambots
Detected by ModSecurity. Request URI: /wp-login.php/ip-redirect/
2019-10-16 21:35:30
146.185.149.245 attack
Oct 16 12:39:42 server sshd\[15430\]: Invalid user oracle from 146.185.149.245
Oct 16 12:39:42 server sshd\[15430\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.185.149.245 
Oct 16 12:39:43 server sshd\[15430\]: Failed password for invalid user oracle from 146.185.149.245 port 34413 ssh2
Oct 16 14:23:01 server sshd\[15633\]: Invalid user smtpuser from 146.185.149.245
Oct 16 14:23:01 server sshd\[15633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.185.149.245 
...
2019-10-16 21:18:59
174.138.58.149 attack
Oct 16 15:07:23 eventyay sshd[21163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.58.149
Oct 16 15:07:25 eventyay sshd[21163]: Failed password for invalid user 2010 from 174.138.58.149 port 52908 ssh2
Oct 16 15:11:40 eventyay sshd[21245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.58.149
...
2019-10-16 21:20:55
192.99.151.33 attackspam
F2B jail: sshd. Time: 2019-10-16 15:14:10, Reported by: VKReport
2019-10-16 21:21:38
117.240.153.138 attack
(imapd) Failed IMAP login from 117.240.153.138 (IN/India/-): 1 in the last 3600 secs
2019-10-16 21:32:11
222.186.175.215 attack
2019-10-16T13:18:50.156599abusebot-8.cloudsearch.cf sshd\[30699\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.215  user=root
2019-10-16 21:41:20
51.77.140.111 attack
Oct 16 15:44:07 server sshd\[7751\]: Failed password for root from 51.77.140.111 port 46170 ssh2
Oct 16 16:44:29 server sshd\[26145\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.ip-51-77-140.eu  user=root
Oct 16 16:44:31 server sshd\[26145\]: Failed password for root from 51.77.140.111 port 60014 ssh2
Oct 16 16:46:17 server sshd\[27011\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.ip-51-77-140.eu  user=root
Oct 16 16:46:19 server sshd\[27011\]: Failed password for root from 51.77.140.111 port 53740 ssh2
...
2019-10-16 21:49:52
162.223.89.163 attackspambots
Port 1433 Scan
2019-10-16 21:52:50

Recently Reported IPs

45.59.221.46 131.161.8.240 131.161.9.9 131.161.9.163
131.161.9.212 131.161.9.217 131.161.9.221 131.161.9.232
78.36.193.193 131.161.8.199 131.161.9.36 131.161.9.115
131.161.9.173 37.228.111.26 37.228.111.147 37.233.99.182
45.70.195.150 45.70.196.138 36.59.116.240 45.70.218.102