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

Region: Bavaria

Country: Germany

Internet Service Provider: Telekom

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

;; QUESTION SECTION:
;79.196.21.245.			IN	A

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

;; Query time: 74 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 26 09:01:22 CST 2022
;; MSG SIZE  rcvd: 106
Host info
245.21.196.79.in-addr.arpa domain name pointer p4fc415f5.dip0.t-ipconnect.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
245.21.196.79.in-addr.arpa	name = p4fc415f5.dip0.t-ipconnect.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
124.156.245.149 attackbotsspam
Unauthorized connection attempt detected from IP address 124.156.245.149 to port 82 [J]
2020-01-18 13:55:59
106.54.124.250 attack
Jan 18 06:20:23 localhost sshd\[26460\]: Invalid user casa from 106.54.124.250
Jan 18 06:20:23 localhost sshd\[26460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.124.250
Jan 18 06:20:25 localhost sshd\[26460\]: Failed password for invalid user casa from 106.54.124.250 port 51334 ssh2
Jan 18 06:22:10 localhost sshd\[26507\]: Invalid user gerrard from 106.54.124.250
Jan 18 06:22:10 localhost sshd\[26507\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.124.250
...
2020-01-18 13:59:59
177.183.80.201 attackbotsspam
Unauthorized connection attempt detected from IP address 177.183.80.201 to port 8081 [J]
2020-01-18 14:16:05
143.255.2.127 attackbotsspam
Unauthorized connection attempt detected from IP address 143.255.2.127 to port 80 [J]
2020-01-18 14:19:39
18.208.129.119 attackspam
Unauthorized connection attempt detected from IP address 18.208.129.119 to port 1900 [J]
2020-01-18 14:10:28
187.59.111.108 attack
Unauthorized connection attempt detected from IP address 187.59.111.108 to port 23 [J]
2020-01-18 13:50:16
31.168.66.223 attack
Unauthorized connection attempt detected from IP address 31.168.66.223 to port 81 [J]
2020-01-18 14:29:46
183.109.176.225 attack
Unauthorized connection attempt detected from IP address 183.109.176.225 to port 4567 [J]
2020-01-18 13:52:14
86.124.130.187 attackbotsspam
Unauthorized connection attempt detected from IP address 86.124.130.187 to port 8000 [J]
2020-01-18 14:24:44
146.88.78.130 attackspambots
Unauthorized connection attempt detected from IP address 146.88.78.130 to port 1433 [J]
2020-01-18 13:54:45
157.245.126.61 attack
Fail2Ban Ban Triggered
2020-01-18 14:18:36
106.13.39.232 attack
Unauthorized connection attempt detected from IP address 106.13.39.232 to port 23 [J]
2020-01-18 14:22:34
191.83.98.184 attackbotsspam
Unauthorized connection attempt detected from IP address 191.83.98.184 to port 80 [J]
2020-01-18 14:14:09
89.21.61.125 attackspambots
Unauthorized connection attempt detected from IP address 89.21.61.125 to port 80 [J]
2020-01-18 14:24:27
14.173.63.191 attackbotsspam
Unauthorized connection attempt detected from IP address 14.173.63.191 to port 82 [J]
2020-01-18 14:10:45

Recently Reported IPs

51.22.72.76 149.92.94.150 247.199.213.77 122.203.240.44
82.153.24.49 206.33.62.46 57.216.97.7 86.139.183.2
115.5.185.26 115.41.11.23 106.32.255.3 186.4.7.111
9.99.177.145 244.30.29.93 192.64.16.42 200.209.168.148
199.41.141.46 238.1.28.87 174.240.80.95 173.31.83.37