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

Region: Madrid

Country: Spain

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

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

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

;; Query time: 105 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 08 06:48:51 CST 2020
;; MSG SIZE  rcvd: 116
Host info
124.93.29.80.in-addr.arpa domain name pointer 124.red-80-29-93.staticip.rima-tde.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
124.93.29.80.in-addr.arpa	name = 124.red-80-29-93.staticip.rima-tde.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
27.120.101.61 attackbots
Automatic report - SSH Brute-Force Attack
2020-02-05 10:19:21
164.52.24.179 attackspambots
Unauthorized connection attempt detected from IP address 164.52.24.179 to port 1111 [J]
2020-02-05 10:02:57
175.184.167.65 attack
Unauthorized connection attempt detected from IP address 175.184.167.65 to port 443 [J]
2020-02-05 10:01:19
168.0.81.99 attackbots
Unauthorized connection attempt detected from IP address 168.0.81.99 to port 23 [J]
2020-02-05 10:24:42
139.162.244.237 attackbotsspam
Unauthorized connection attempt detected from IP address 139.162.244.237 to port 2404 [J]
2020-02-05 10:03:52
110.52.215.86 attack
$f2bV_matches
2020-02-05 10:31:59
78.163.113.32 attackbots
Unauthorized connection attempt detected from IP address 78.163.113.32 to port 23 [J]
2020-02-05 10:38:15
51.198.120.72 attackbotsspam
Unauthorized connection attempt detected from IP address 51.198.120.72 to port 23 [J]
2020-02-05 10:15:41
79.46.82.64 attack
Unauthorized connection attempt detected from IP address 79.46.82.64 to port 23 [J]
2020-02-05 10:12:56
46.21.69.98 attackspambots
Unauthorized connection attempt detected from IP address 46.21.69.98 to port 8080 [J]
2020-02-05 10:16:55
124.95.13.229 attackspambots
Unauthorized connection attempt detected from IP address 124.95.13.229 to port 23 [J]
2020-02-05 10:04:23
47.100.92.157 attackspambots
Unauthorized connection attempt detected from IP address 47.100.92.157 to port 1433 [J]
2020-02-05 10:42:02
134.249.121.243 attackbots
Unauthorized connection attempt detected from IP address 134.249.121.243 to port 2220 [J]
2020-02-05 10:27:28
87.140.6.227 attack
Unauthorized connection attempt detected from IP address 87.140.6.227 to port 2220 [J]
2020-02-05 10:36:17
106.12.209.38 attackspam
Feb  5 04:14:42 server sshd\[2487\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.209.38  user=root
Feb  5 04:14:44 server sshd\[2487\]: Failed password for root from 106.12.209.38 port 44960 ssh2
Feb  5 04:25:43 server sshd\[4888\]: Invalid user matt from 106.12.209.38
Feb  5 04:25:43 server sshd\[4888\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.209.38 
Feb  5 04:25:44 server sshd\[4888\]: Failed password for invalid user matt from 106.12.209.38 port 41296 ssh2
...
2020-02-05 10:32:41

Recently Reported IPs

194.13.85.251 223.195.23.20 104.172.179.81 81.91.61.10
1.72.83.132 196.233.112.7 115.64.42.22 124.82.116.113
186.145.55.139 108.161.91.67 110.42.97.18 212.180.172.122
150.109.112.223 52.32.2.94 203.51.135.43 93.175.123.35
190.229.232.192 90.232.72.167 121.45.59.167 201.177.157.174