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

;; QUESTION SECTION:
;166.5.134.245.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 04:00:24 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 245.134.5.166.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 245.134.5.166.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
132.232.29.208 attackspam
Jan  5 03:42:34 server sshd\[4264\]: Invalid user test from 132.232.29.208
Jan  5 03:42:34 server sshd\[4264\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.29.208 
Jan  5 03:42:36 server sshd\[4264\]: Failed password for invalid user test from 132.232.29.208 port 43520 ssh2
Jan  6 02:26:08 server sshd\[1116\]: Invalid user ip from 132.232.29.208
Jan  6 02:26:08 server sshd\[1116\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.29.208 
...
2020-01-06 09:51:33
140.143.222.95 attack
Unauthorized connection attempt detected from IP address 140.143.222.95 to port 2220 [J]
2020-01-06 13:18:07
177.106.182.172 attackbots
Unauthorized connection attempt detected from IP address 177.106.182.172 to port 22 [J]
2020-01-06 13:01:28
104.248.117.234 attack
Unauthorized connection attempt detected from IP address 104.248.117.234 to port 2220 [J]
2020-01-06 09:51:07
220.172.158.145 attack
Unauthorized connection attempt detected from IP address 220.172.158.145 to port 23 [J]
2020-01-06 13:00:08
167.71.57.11 attack
Unauthorized connection attempt detected from IP address 167.71.57.11 to port 23 [J]
2020-01-06 13:17:36
123.206.44.110 attack
Unauthorized connection attempt detected from IP address 123.206.44.110 to port 2220 [J]
2020-01-06 13:19:47
162.244.14.105 attackspambots
Unauthorized connection attempt from IP address 162.244.14.105 on Port 445(SMB)
2020-01-06 09:48:40
202.169.235.71 attack
Unauthorized connection attempt detected from IP address 202.169.235.71 to port 80 [J]
2020-01-06 13:10:05
154.73.160.87 attackspam
Unauthorized connection attempt from IP address 154.73.160.87 on Port 445(SMB)
2020-01-06 10:01:49
119.27.165.134 attackbotsspam
Unauthorized connection attempt detected from IP address 119.27.165.134 to port 2220 [J]
2020-01-06 13:21:03
195.191.183.60 attackspambots
Unauthorized connection attempt detected from IP address 195.191.183.60 to port 8080 [J]
2020-01-06 13:11:55
188.210.158.236 attackspam
Unauthorized connection attempt detected from IP address 188.210.158.236 to port 8080 [J]
2020-01-06 13:12:24
201.190.33.75 attackbots
Unauthorized connection attempt detected from IP address 201.190.33.75 to port 23 [J]
2020-01-06 13:10:52
14.232.243.153 attackbots
Unauthorized connection attempt from IP address 14.232.243.153 on Port 445(SMB)
2020-01-06 09:59:03

Recently Reported IPs

84.66.137.56 165.45.154.198 134.7.37.116 131.84.235.253
34.220.3.37 198.101.167.70 221.249.181.178 114.187.214.61
47.76.218.74 179.239.67.247 4.213.53.11 220.78.197.252
231.8.241.244 190.10.17.122 253.163.202.225 87.97.72.147
86.49.68.145 70.36.143.120 246.218.250.88 97.234.245.43