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: Deutsche Telekom AG

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
Type Details Datetime
attackbotsspam
Jun 26 06:34:21 mail1 sshd[29753]: Invalid user pi from 80.129.48.244 port 34118
Jun 26 06:34:21 mail1 sshd[29754]: Invalid user pi from 80.129.48.244 port 34120
Jun 26 06:34:21 mail1 sshd[29753]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.129.48.244
Jun 26 06:34:21 mail1 sshd[29754]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.129.48.244


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=80.129.48.244
2020-06-26 13:07:12
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 80.129.48.244
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50316
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 178 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jun 26 13:07:00 CST 2020
;; MSG SIZE  rcvd: 117
Host info
244.48.129.80.in-addr.arpa domain name pointer p508130f4.dip0.t-ipconnect.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
244.48.129.80.in-addr.arpa	name = p508130f4.dip0.t-ipconnect.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.78.181.154 attackbotsspam
Unauthorized connection attempt detected from IP address 103.78.181.154 to port 80 [J]
2020-01-07 16:36:28
148.72.212.161 attackbots
Unauthorized connection attempt detected from IP address 148.72.212.161 to port 2220 [J]
2020-01-07 16:57:05
5.178.188.78 attack
Unauthorized connection attempt detected from IP address 5.178.188.78 to port 8080 [J]
2020-01-07 17:13:19
62.219.129.114 attackspambots
Unauthorized connection attempt detected from IP address 62.219.129.114 to port 81 [J]
2020-01-07 17:08:26
81.198.14.254 attack
5555/tcp
[2020-01-07]1pkt
2020-01-07 17:07:03
112.236.57.4 attack
Unauthorized connection attempt detected from IP address 112.236.57.4 to port 23 [J]
2020-01-07 17:02:38
5.77.201.200 attackspambots
Unauthorized connection attempt detected from IP address 5.77.201.200 to port 2323 [J]
2020-01-07 16:44:39
189.0.44.244 attack
Unauthorized connection attempt detected from IP address 189.0.44.244 to port 23 [J]
2020-01-07 16:51:16
106.12.23.198 attackbots
Unauthorized connection attempt detected from IP address 106.12.23.198 to port 2220 [J]
2020-01-07 17:04:31
188.165.237.136 attackspam
Unauthorized connection attempt detected from IP address 188.165.237.136 to port 1741 [J]
2020-01-07 16:51:37
202.96.137.99 attackbots
Unauthorized connection attempt detected from IP address 202.96.137.99 to port 1433 [J]
2020-01-07 16:48:36
51.75.37.173 attackbots
Unauthorized connection attempt detected from IP address 51.75.37.173 to port 2220 [J]
2020-01-07 16:40:36
211.34.44.61 attackspam
Unauthorized connection attempt detected from IP address 211.34.44.61 to port 2220 [J]
2020-01-07 16:48:06
41.80.35.17 attackbots
SSH Brute Force
2020-01-07 16:42:46
103.96.51.15 attackspambots
Unauthorized connection attempt detected from IP address 103.96.51.15 to port 8080 [J]
2020-01-07 16:36:02

Recently Reported IPs

190.235.110.249 183.83.10.33 45.76.65.153 181.39.37.99
89.248.162.214 77.88.5.33 64.227.50.96 223.204.246.3
177.203.150.26 47.254.43.7 40.92.253.95 47.254.36.89
47.254.24.77 47.254.22.192 47.254.47.223 47.254.35.118
138.68.236.156 64.64.231.27 177.139.102.174 106.52.251.24