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

;; QUESTION SECTION:
;129.66.1.161.			IN	A

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

;; Query time: 29 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 12:36:06 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 161.1.66.129.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 161.1.66.129.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
197.248.2.229 attack
Nov 24 09:08:47 nextcloud sshd\[5860\]: Invalid user git from 197.248.2.229
Nov 24 09:08:47 nextcloud sshd\[5860\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.248.2.229
Nov 24 09:08:49 nextcloud sshd\[5860\]: Failed password for invalid user git from 197.248.2.229 port 40102 ssh2
...
2019-11-24 18:30:07
85.212.77.60 attackbotsspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/85.212.77.60/ 
 
 DE - 1H : (42)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : DE 
 NAME ASN : ASN12312 
 
 IP : 85.212.77.60 
 
 CIDR : 85.212.0.0/15 
 
 PREFIX COUNT : 28 
 
 UNIQUE IP COUNT : 959744 
 
 
 ATTACKS DETECTED ASN12312 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-24 07:23:02 
 
 INFO : Port SSH 22 Scan Detected and Blocked by ADMIN  - data recovery
2019-11-24 18:51:53
111.113.19.138 attackspambots
SSH login attempt with user test
2019-11-24 18:42:58
217.72.6.246 attack
SSH login attempt with user pi
2019-11-24 18:34:15
178.220.4.181 attackspambots
Automatic report - Port Scan Attack
2019-11-24 18:45:09
187.217.199.20 attack
Nov 24 09:01:53 l02a sshd[15604]: Invalid user ching from 187.217.199.20
Nov 24 09:01:53 l02a sshd[15604]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.217.199.20 
Nov 24 09:01:53 l02a sshd[15604]: Invalid user ching from 187.217.199.20
Nov 24 09:01:54 l02a sshd[15604]: Failed password for invalid user ching from 187.217.199.20 port 38278 ssh2
2019-11-24 18:31:29
138.68.219.40 attack
port scan and connect, tcp 8080 (http-proxy)
2019-11-24 18:51:36
222.186.175.202 attackbots
2019-11-23 UTC: 4x - (4x)
2019-11-24 18:53:43
190.98.227.243 attackspambots
Port 1433 Scan
2019-11-24 18:25:49
112.91.254.3 attackspam
2019-11-24T02:13:23.3826991495-001 sshd\[38598\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.91.254.3  user=root
2019-11-24T02:13:25.2733451495-001 sshd\[38598\]: Failed password for root from 112.91.254.3 port 44698 ssh2
2019-11-24T02:20:18.8111061495-001 sshd\[38833\]: Invalid user nobby from 112.91.254.3 port 48500
2019-11-24T02:20:18.8193581495-001 sshd\[38833\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.91.254.3
2019-11-24T02:20:21.0164211495-001 sshd\[38833\]: Failed password for invalid user nobby from 112.91.254.3 port 48500 ssh2
2019-11-24T02:27:04.5096311495-001 sshd\[39060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.91.254.3  user=mail
...
2019-11-24 18:46:05
134.209.186.72 attackspam
Nov 24 12:45:22 hosting sshd[9782]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.186.72  user=backup
Nov 24 12:45:24 hosting sshd[9782]: Failed password for backup from 134.209.186.72 port 48500 ssh2
...
2019-11-24 18:46:48
159.203.201.184 attack
159.203.201.184 was recorded 5 times by 5 hosts attempting to connect to the following ports: 8080. Incident counter (4h, 24h, all-time): 5, 6, 136
2019-11-24 18:27:55
112.175.184.45 attack
112.175.184.45 - - \[24/Nov/2019:07:59:21 +0100\] "POST /wp-login.php HTTP/1.0" 200 7411 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
112.175.184.45 - - \[24/Nov/2019:07:59:24 +0100\] "POST /wp-login.php HTTP/1.0" 200 7226 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
112.175.184.45 - - \[24/Nov/2019:07:59:27 +0100\] "POST /wp-login.php HTTP/1.0" 200 7223 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-24 18:36:17
177.69.237.49 attackbots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.69.237.49  user=root
Failed password for root from 177.69.237.49 port 51740 ssh2
Invalid user phoung from 177.69.237.49 port 59466
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.69.237.49
Failed password for invalid user phoung from 177.69.237.49 port 59466 ssh2
2019-11-24 18:35:56
59.25.197.162 attackbots
2019-11-24T06:58:07.445417abusebot-5.cloudsearch.cf sshd\[15285\]: Invalid user bjorn from 59.25.197.162 port 56562
2019-11-24 18:32:52

Recently Reported IPs

176.143.150.174 235.116.30.75 136.45.132.223 35.140.51.227
175.124.183.102 125.226.84.144 6.92.157.54 45.91.244.12
230.67.161.43 224.56.215.110 157.198.96.144 218.208.214.222
203.51.137.111 200.219.33.197 116.182.26.51 67.102.38.223
206.62.232.119 29.193.88.185 109.38.98.54 148.200.4.74