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

;; QUESTION SECTION:
;80.131.157.219.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jan 25 21:23:26 CST 2025
;; MSG SIZE  rcvd: 107
Host info
219.157.131.80.in-addr.arpa domain name pointer p50839ddb.dip0.t-ipconnect.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
219.157.131.80.in-addr.arpa	name = p50839ddb.dip0.t-ipconnect.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
192.241.235.26 attack
SSH Bruteforce Attempt on Honeypot
2020-10-05 06:07:20
90.127.136.228 attackbots
SSH Invalid Login
2020-10-05 06:19:17
83.12.171.68 attackspam
Oct  4 23:09:28 pornomens sshd\[7344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.12.171.68  user=root
Oct  4 23:09:30 pornomens sshd\[7344\]: Failed password for root from 83.12.171.68 port 16271 ssh2
Oct  4 23:24:40 pornomens sshd\[7492\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.12.171.68  user=root
...
2020-10-05 05:53:42
162.243.128.49 attackspambots
TCP port : 79
2020-10-05 05:46:48
162.243.128.177 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-10-05 06:11:06
95.9.227.216 attack
Automatic report - Port Scan Attack
2020-10-05 05:59:48
111.72.193.182 attack
Oct  4 00:53:58 srv01 postfix/smtpd\[30998\]: warning: unknown\[111.72.193.182\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  4 00:54:10 srv01 postfix/smtpd\[30998\]: warning: unknown\[111.72.193.182\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  4 00:54:26 srv01 postfix/smtpd\[30998\]: warning: unknown\[111.72.193.182\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  4 00:54:45 srv01 postfix/smtpd\[30998\]: warning: unknown\[111.72.193.182\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  4 00:54:57 srv01 postfix/smtpd\[30998\]: warning: unknown\[111.72.193.182\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-05 05:49:10
165.232.106.249 attack
Oct  3 23:35:00 jane sshd[21582]: Failed password for root from 165.232.106.249 port 50264 ssh2
...
2020-10-05 05:48:12
196.52.43.123 attackspambots
6363/tcp 9042/tcp 9000/tcp...
[2020-08-04/10-03]65pkt,50pt.(tcp),2pt.(udp)
2020-10-05 06:00:35
139.59.161.78 attackbotsspam
$f2bV_matches
2020-10-05 05:57:30
139.59.83.179 attackspam
Oct  4 17:26:42 NPSTNNYC01T sshd[26897]: Failed password for root from 139.59.83.179 port 54556 ssh2
Oct  4 17:29:44 NPSTNNYC01T sshd[27299]: Failed password for root from 139.59.83.179 port 40056 ssh2
...
2020-10-05 06:10:19
192.3.255.139 attackbots
Oct  4 18:59:31 mx sshd[379]: Failed password for root from 192.3.255.139 port 47580 ssh2
2020-10-05 06:11:42
222.223.160.18 attackspambots
 TCP (SYN) 222.223.160.18:2757 -> port 1433, len 44
2020-10-05 06:00:13
208.109.11.224 attackbotsspam
Attempt to run wp-login.php
2020-10-05 06:12:19
45.55.65.92 attack
firewall-block, port(s): 23786/tcp
2020-10-05 06:04:49

Recently Reported IPs

227.179.21.246 12.225.45.55 24.161.59.173 90.140.115.43
163.238.229.166 18.136.122.249 165.216.178.72 230.206.120.17
186.2.159.228 242.229.15.115 9.183.250.92 81.236.104.173
188.96.223.187 208.206.202.78 96.149.98.236 87.69.148.160
81.124.132.87 143.60.59.228 152.140.20.202 104.113.149.249