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

;; QUESTION SECTION:
;131.196.141.1.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 05:31:27 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 1.141.196.131.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 1.141.196.131.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
200.219.152.41 attackbots
IMAP
2020-01-14 07:35:50
221.229.219.188 attackbots
2020-01-13 22:19:28,429 fail2ban.actions        [2870]: NOTICE  [sshd] Ban 221.229.219.188
2020-01-13 22:53:58,004 fail2ban.actions        [2870]: NOTICE  [sshd] Ban 221.229.219.188
2020-01-13 23:28:41,844 fail2ban.actions        [2870]: NOTICE  [sshd] Ban 221.229.219.188
2020-01-14 00:04:40,553 fail2ban.actions        [2870]: NOTICE  [sshd] Ban 221.229.219.188
2020-01-14 00:41:15,298 fail2ban.actions        [2870]: NOTICE  [sshd] Ban 221.229.219.188
...
2020-01-14 08:09:32
103.94.217.214 attack
Unauthorized connection attempt detected from IP address 103.94.217.214 to port 2220 [J]
2020-01-14 07:48:49
103.74.123.6 attackspambots
WordPress wp-login brute force :: 103.74.123.6 0.104 BYPASS [13/Jan/2020:21:21:57  0000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 2287 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-01-14 07:49:03
113.173.166.15 attackspam
Jan 13 22:10:53 linuxrulz sshd[17545]: Invalid user admin from 113.173.166.15 port 48385
Jan 13 22:10:53 linuxrulz sshd[17545]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.173.166.15
Jan 13 22:10:55 linuxrulz sshd[17545]: Failed password for invalid user admin from 113.173.166.15 port 48385 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=113.173.166.15
2020-01-14 07:33:52
218.92.0.184 attack
20/1/13@18:51:12: FAIL: IoT-SSH address from=218.92.0.184
...
2020-01-14 07:53:05
198.71.241.2 attackspambots
xmlrpc attack
2020-01-14 07:36:04
185.175.93.18 attackbotsspam
Multiport scan : 17 ports scanned 2789 3989 10789 11089 21189 21689 28389 34389 36489 41089 42689 44689 53589 57489 57989 59289 60689
2020-01-14 07:44:30
77.247.108.91 attackspambots
77.247.108.91 was recorded 8 times by 2 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 8, 49, 914
2020-01-14 07:54:46
168.232.158.30 attackspam
$f2bV_matches
2020-01-14 07:48:04
132.232.74.106 attackbotsspam
Unauthorized connection attempt detected from IP address 132.232.74.106 to port 2220 [J]
2020-01-14 07:48:17
118.71.153.104 attackspambots
1578950504 - 01/13/2020 22:21:44 Host: 118.71.153.104/118.71.153.104 Port: 445 TCP Blocked
2020-01-14 07:57:57
84.1.159.116 attackspam
Jan 13 12:49:49 foo sshd[9914]: Address 84.1.159.116 maps to checktls.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Jan 13 12:49:49 foo sshd[9914]: Invalid user abe from 84.1.159.116
Jan 13 12:49:49 foo sshd[9914]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.1.159.116 
Jan 13 12:49:51 foo sshd[9914]: Failed password for invalid user abe from 84.1.159.116 port 44658 ssh2
Jan 13 12:49:52 foo sshd[9914]: Received disconnect from 84.1.159.116: 11: Bye Bye [preauth]
Jan 13 13:18:09 foo sshd[11381]: Address 84.1.159.116 maps to checktls.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Jan 13 13:18:09 foo sshd[11381]: Invalid user jetty from 84.1.159.116
Jan 13 13:18:09 foo sshd[11381]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.1.159.116 
Jan 13 13:18:11 foo sshd[11381]: Failed password for invalid user jetty from 84.1.159.116........
-------------------------------
2020-01-14 07:31:47
107.173.209.247 attackspam
Jan 14 00:06:15 amit sshd\[11019\]: Invalid user bo from 107.173.209.247
Jan 14 00:06:15 amit sshd\[11019\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.173.209.247
Jan 14 00:06:16 amit sshd\[11019\]: Failed password for invalid user bo from 107.173.209.247 port 42140 ssh2
...
2020-01-14 07:33:10
80.82.65.74 attackbots
Multiport scan : 16 ports scanned 999 3629 5003 6666 6667 8197 8888 8908 11337 18118 39880 41766 51437 59341 63000 63253
2020-01-14 07:45:17

Recently Reported IPs

131.196.14.203 131.196.14.231 131.196.14.235 131.196.14.232
131.196.141.100 131.196.14.82 131.196.141.10 118.172.237.113
131.196.141.103 131.196.141.104 131.196.141.106 118.172.237.141
131.196.141.108 131.196.141.11 131.196.141.110 131.196.141.112
131.196.141.118 131.196.141.123 131.196.141.12 131.196.141.116