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

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

;; QUESTION SECTION:
;169.229.53.66.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 26 20:00:30 CST 2022
;; MSG SIZE  rcvd: 106
Host info
66.53.229.169.in-addr.arpa domain name pointer plant_const.berkeley.edu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
66.53.229.169.in-addr.arpa	name = plant_const.berkeley.edu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
37.34.183.243 attackspam
" "
2019-07-24 07:39:40
104.140.188.14 attackspambots
Honeypot attack, port: 23, PTR: shi1a3l.shield8lunch.press.
2019-07-24 07:32:54
14.186.223.82 attackspam
Brute force attempt
2019-07-24 07:33:30
104.144.28.161 attackspambots
(From townsendmbennie@gmail.com) Hello there!

I'm a freelance digital marketing specialist, and I'm offering you my SEO services at an affordable price. My eight years of experience in this field have taught me everything there is to know about getting websites to the top of search engine results. Making sure that your business website appears on top of search results is essential since not only can this can increase the amount of traffic you get, but it also boosts growth.

I know about all the algorithms utilized by Google like the back of my hand and I know exactly what strategies can make your site rank higher in search engines. If you're interested, I'll provide you with a free consultation to conduct an assessment about where your site currently stands, what needs to be done, and what to expect in terms of results if you're interested. 

All the information that I'll be giving you will be helpful for your business whether or not you want to take advantage of my services. Kindly reply to let me kn
2019-07-24 08:09:59
61.145.56.28 attackspambots
Jul 23 14:38:30 xxx sshd[30794]: Invalid user odoo from 61.145.56.28 port 45850
Jul 23 14:38:30 xxx sshd[30794]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.145.56.28
Jul 23 14:38:33 xxx sshd[30794]: Failed password for invalid user odoo from 61.145.56.28 port 45850 ssh2
Jul 23 14:38:33 xxx sshd[30794]: Received disconnect from 61.145.56.28 port 45850:11: Bye Bye [preauth]
Jul 23 14:38:33 xxx sshd[30794]: Disconnected from 61.145.56.28 port 45850 [preauth]
Jul 23 15:10:48 xxx sshd[928]: Invalid user postgres from 61.145.56.28 port 36840
Jul 23 15:10:48 xxx sshd[928]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.145.56.28
Jul 23 15:10:50 xxx sshd[928]: Failed password for invalid user postgres from 61.145.56.28 port 36840 ssh2
Jul 23 15:10:51 xxx sshd[928]: Received disconnect from 61.145.56.28 port 36840:11: Bye Bye [preauth]
Jul 23 15:10:51 xxx sshd[928]: Disconnected from 61.1........
-------------------------------
2019-07-24 07:41:10
164.132.24.138 attackbotsspam
SSH Brute Force
2019-07-24 07:35:58
45.35.104.64 attackspam
Jul 23 22:16:24 [snip] sshd[22316]: Invalid user sl from 45.35.104.64 port 37952
Jul 23 22:16:24 [snip] sshd[22316]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.35.104.64
Jul 23 22:16:26 [snip] sshd[22316]: Failed password for invalid user sl from 45.35.104.64 port 37952 ssh2[...]
2019-07-24 08:06:51
160.16.204.83 attack
WordPress brute force
2019-07-24 08:08:02
175.153.251.247 attack
DATE:2019-07-23_22:16:05, IP:175.153.251.247, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-07-24 08:20:28
148.70.60.239 attackspam
ft-1848-basketball.de 148.70.60.239 \[23/Jul/2019:22:16:18 +0200\] "POST /wp-login.php HTTP/1.1" 200 2164 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
ft-1848-basketball.de 148.70.60.239 \[23/Jul/2019:22:16:20 +0200\] "POST /wp-login.php HTTP/1.1" 200 2136 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-07-24 08:09:00
219.128.20.71 attackspam
Jul 23 11:44:26 hgb10301 sshd[25004]: Bad protocol version identification '' from 219.128.20.71 port 42894
Jul 23 11:44:28 hgb10301 sshd[25005]: Invalid user support from 219.128.20.71 port 43024
Jul 23 11:44:29 hgb10301 sshd[25005]: Failed password for invalid user support from 219.128.20.71 port 43024 ssh2
Jul 23 11:44:30 hgb10301 sshd[25005]: Connection closed by 219.128.20.71 port 43024 [preauth]
Jul 23 11:44:31 hgb10301 sshd[25007]: Invalid user netscreen from 219.128.20.71 port 43835
Jul 23 11:44:33 hgb10301 sshd[25007]: Failed password for invalid user netscreen from 219.128.20.71 port 43835 ssh2
Jul 23 11:44:34 hgb10301 sshd[25007]: Connection closed by 219.128.20.71 port 43835 [preauth]
Jul 23 11:44:35 hgb10301 sshd[25009]: Invalid user nexthink from 219.128.20.71 port 44779
Jul 23 11:44:37 hgb10301 sshd[25009]: Failed password for invalid user nexthink from 219.128.20.71 port 44779 ssh2
Jul 23 11:44:37 hgb10301 sshd[25009]: Connection closed by 219.128.20.71 p........
-------------------------------
2019-07-24 07:35:03
199.195.249.6 attackspambots
Jul 24 01:55:55 eventyay sshd[5849]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.249.6
Jul 24 01:55:57 eventyay sshd[5849]: Failed password for invalid user aan from 199.195.249.6 port 39656 ssh2
Jul 24 02:00:17 eventyay sshd[7102]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.249.6
...
2019-07-24 08:10:58
140.143.198.123 attack
Jul 23 22:16:36 web2 sshd[20559]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.198.123
Jul 23 22:16:38 web2 sshd[20559]: Failed password for invalid user test from 140.143.198.123 port 48248 ssh2
2019-07-24 07:58:58
36.153.89.206 attack
2019-07-23T23:35:58.798763abusebot-6.cloudsearch.cf sshd\[5375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.153.89.206  user=root
2019-07-24 07:41:52
105.73.80.135 attackbots
Jul 23 22:05:35 Proxmox sshd\[12048\]: User admin from 105.73.80.135 not allowed because not listed in AllowUsers
Jul 23 22:05:35 Proxmox sshd\[12048\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=105.73.80.135  user=admin
Jul 23 22:05:37 Proxmox sshd\[12048\]: Failed password for invalid user admin from 105.73.80.135 port 14190 ssh2
Jul 23 22:16:57 Proxmox sshd\[29543\]: Invalid user zabbix from 105.73.80.135 port 14191
Jul 23 22:16:57 Proxmox sshd\[29543\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=105.73.80.135
Jul 23 22:16:59 Proxmox sshd\[29543\]: Failed password for invalid user zabbix from 105.73.80.135 port 14191 ssh2
2019-07-24 07:43:52

Recently Reported IPs

169.229.53.61 169.229.53.76 169.229.53.69 169.229.53.92
169.229.53.88 169.229.130.244 169.229.37.116 169.229.37.227
169.229.37.231 169.229.38.57 169.229.38.44 169.229.38.66
169.229.38.87 169.229.159.55 169.229.153.233 169.229.147.199
169.229.152.90 169.229.149.127 169.229.152.246 169.229.151.52