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

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;141.2.200.131.			IN	A

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

;; Query time: 75 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jul 28 23:59:30 CST 2020
;; MSG SIZE  rcvd: 117
Host info
131.200.2.141.in-addr.arpa domain name pointer dict0131.kgu.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
131.200.2.141.in-addr.arpa	name = dict0131.kgu.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
58.248.118.4 attackspam
Unauthorised access (Nov  4) SRC=58.248.118.4 LEN=40 TTL=49 ID=41862 TCP DPT=8080 WINDOW=40375 SYN 
Unauthorised access (Nov  3) SRC=58.248.118.4 LEN=40 TTL=49 ID=56078 TCP DPT=8080 WINDOW=40375 SYN
2019-11-04 07:52:30
180.249.200.210 attackbotsspam
Unauthorized connection attempt from IP address 180.249.200.210 on Port 445(SMB)
2019-11-04 07:32:32
188.166.48.121 attackspam
Nov  3 12:56:47 wbs sshd\[23793\]: Invalid user test2012 from 188.166.48.121
Nov  3 12:56:47 wbs sshd\[23793\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.48.121
Nov  3 12:56:49 wbs sshd\[23793\]: Failed password for invalid user test2012 from 188.166.48.121 port 43106 ssh2
Nov  3 13:00:47 wbs sshd\[24142\]: Invalid user oseias123 from 188.166.48.121
Nov  3 13:00:47 wbs sshd\[24142\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.48.121
2019-11-04 07:53:00
115.29.11.56 attack
Nov  4 00:33:26 h2177944 sshd\[26589\]: Invalid user qwe123, from 115.29.11.56 port 58481
Nov  4 00:33:26 h2177944 sshd\[26589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.29.11.56
Nov  4 00:33:27 h2177944 sshd\[26589\]: Failed password for invalid user qwe123, from 115.29.11.56 port 58481 ssh2
Nov  4 00:38:29 h2177944 sshd\[26740\]: Invalid user 123 from 115.29.11.56 port 49061
...
2019-11-04 07:51:46
80.82.77.132 attackspam
Excessive Port-Scanning
2019-11-04 08:08:11
49.207.180.197 attackbotsspam
Invalid user h from 49.207.180.197 port 18526
2019-11-04 07:56:24
180.250.18.87 attackbots
2019-11-04T00:01:42.169141abusebot-4.cloudsearch.cf sshd\[21219\]: Invalid user di from 180.250.18.87 port 47336
2019-11-04 08:05:36
202.71.176.134 attackbots
Nov  3 13:40:20 php1 sshd\[1731\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.176.71.202.sta.prodatanet.com.ph  user=root
Nov  3 13:40:22 php1 sshd\[1731\]: Failed password for root from 202.71.176.134 port 39314 ssh2
Nov  3 13:44:55 php1 sshd\[2275\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.176.71.202.sta.prodatanet.com.ph  user=root
Nov  3 13:44:57 php1 sshd\[2275\]: Failed password for root from 202.71.176.134 port 50112 ssh2
Nov  3 13:49:30 php1 sshd\[2775\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.176.71.202.sta.prodatanet.com.ph  user=root
2019-11-04 08:07:34
121.204.185.106 attack
Nov  3 13:57:54 web1 sshd\[821\]: Invalid user nova from 121.204.185.106
Nov  3 13:57:54 web1 sshd\[821\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.204.185.106
Nov  3 13:57:56 web1 sshd\[821\]: Failed password for invalid user nova from 121.204.185.106 port 57133 ssh2
Nov  3 14:01:52 web1 sshd\[1156\]: Invalid user xs from 121.204.185.106
Nov  3 14:01:52 web1 sshd\[1156\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.204.185.106
2019-11-04 08:04:52
221.162.255.86 attackbots
2019-11-03T23:07:14.412697abusebot-5.cloudsearch.cf sshd\[8331\]: Invalid user bjorn from 221.162.255.86 port 54758
2019-11-04 07:59:34
49.235.76.69 attack
Nov  3 23:29:25 mc1 kernel: \[4106473.203709\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=49.235.76.69 DST=159.69.205.51 LEN=52 TOS=0x00 PREC=0x00 TTL=109 ID=24196 DF PROTO=TCP SPT=53423 DPT=243 WINDOW=8192 RES=0x00 SYN URGP=0 
Nov  3 23:29:25 mc1 kernel: \[4106473.219892\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=49.235.76.69 DST=159.69.205.51 LEN=52 TOS=0x00 PREC=0x00 TTL=109 ID=24198 DF PROTO=TCP SPT=53425 DPT=243 WINDOW=8192 RES=0x00 SYN URGP=0 
Nov  3 23:29:25 mc1 kernel: \[4106473.235903\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=49.235.76.69 DST=159.69.205.51 LEN=52 TOS=0x00 PREC=0x00 TTL=109 ID=24200 DF PROTO=TCP SPT=53427 DPT=64341 WINDOW=8192 RES=0x00 SYN URGP=0 
Nov  3 23:29:25 mc1 kernel: \[4106473.251716\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=49.235.76.69 DST=159.69.205.51 LEN=52 TOS=0x00 PREC=0x00 TTL=109 ID=24202 DF PROTO=TCP S
...
2019-11-04 07:52:48
146.185.181.64 attackbotsspam
Nov  3 23:13:44 venus sshd\[17480\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.185.181.64  user=root
Nov  3 23:13:46 venus sshd\[17480\]: Failed password for root from 146.185.181.64 port 38251 ssh2
Nov  3 23:17:13 venus sshd\[17534\]: Invalid user postgres5 from 146.185.181.64 port 57558
...
2019-11-04 07:39:20
106.12.33.50 attackbots
SSH Brute-Force reported by Fail2Ban
2019-11-04 07:41:30
167.71.182.13 attackbotsspam
Wordpress XMLRPC attack
2019-11-04 08:06:49
3.225.74.213 attack
3.225.74.213 was recorded 5 times by 2 hosts attempting to connect to the following ports: 4243,2375,2376. Incident counter (4h, 24h, all-time): 5, 5, 21
2019-11-04 13:00:35

Recently Reported IPs

45.79.251.85 187.212.158.87 65.139.99.169 179.191.153.245
241.217.50.185 48.0.30.193 216.21.186.81 201.165.215.207
95.161.125.74 166.45.33.229 69.94.156.34 38.167.122.252
35.80.61.58 178.33.194.112 94.74.181.118 49.88.65.64
164.160.33.164 139.59.41.229 83.218.126.222 140.249.23.235