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: United States of America (the)

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

;; QUESTION SECTION:
;99.55.53.29.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 23:01:46 CST 2025
;; MSG SIZE  rcvd: 104
Host info
b'Host 29.53.55.99.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 29.53.55.99.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
207.44.55.52 attackspam
Unauthorized connection attempt detected from IP address 207.44.55.52 to port 80 [J]
2020-02-05 16:52:22
222.186.42.136 attackspambots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.136  user=root
Failed password for root from 222.186.42.136 port 20591 ssh2
Failed password for root from 222.186.42.136 port 20591 ssh2
Failed password for root from 222.186.42.136 port 20591 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.136  user=root
Failed password for root from 222.186.42.136 port 24732 ssh2
Failed password for root from 222.186.42.136 port 24732 ssh2
Failed password for root from 222.186.42.136 port 24732 ssh2
2020-02-05 16:48:50
103.251.208.121 attackspambots
Unauthorized connection attempt detected from IP address 103.251.208.121 to port 80 [J]
2020-02-05 17:04:07
211.23.234.153 attackbotsspam
Unauthorized connection attempt detected from IP address 211.23.234.153 to port 4567 [J]
2020-02-05 16:51:54
122.165.145.141 attackspam
Unauthorized connection attempt detected from IP address 122.165.145.141 to port 23 [J]
2020-02-05 17:23:55
51.91.56.133 attackspam
Unauthorized connection attempt detected from IP address 51.91.56.133 to port 2220 [J]
2020-02-05 17:08:48
80.81.85.205 attack
$f2bV_matches
2020-02-05 17:05:34
110.74.146.135 attackbotsspam
Unauthorized connection attempt detected from IP address 110.74.146.135 to port 1433 [J]
2020-02-05 17:02:48
179.97.196.89 attackspambots
Unauthorized connection attempt detected from IP address 179.97.196.89 to port 8080 [J]
2020-02-05 16:55:55
179.106.102.172 attackbots
Unauthorized connection attempt detected from IP address 179.106.102.172 to port 8080 [J]
2020-02-05 16:55:28
180.96.28.87 attackspam
Unauthorized connection attempt detected from IP address 180.96.28.87 to port 2220 [J]
2020-02-05 17:17:44
181.112.218.70 attackbotsspam
Unauthorized connection attempt detected from IP address 181.112.218.70 to port 23 [J]
2020-02-05 17:17:12
43.252.145.234 attackbotsspam
Unauthorized connection attempt detected from IP address 43.252.145.234 to port 8080 [J]
2020-02-05 17:09:46
167.250.177.233 attack
Unauthorized connection attempt detected from IP address 167.250.177.233 to port 5555 [J]
2020-02-05 17:20:29
61.2.177.247 attack
Unauthorized connection attempt detected from IP address 61.2.177.247 to port 81 [J]
2020-02-05 17:31:29

Recently Reported IPs

141.89.231.65 43.54.48.48 123.174.86.74 205.33.85.91
86.54.97.147 186.31.195.50 145.136.5.158 27.255.165.160
103.180.9.227 68.156.182.44 176.217.7.144 36.93.25.219
164.142.111.17 254.107.48.200 9.148.179.103 42.17.116.129
204.74.231.90 177.4.118.175 179.6.153.247 35.119.3.55