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

;; QUESTION SECTION:
;169.229.214.244.		IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jun 27 19:10:29 CST 2022
;; MSG SIZE  rcvd: 108
Host info
244.214.229.169.in-addr.arpa domain name pointer fixed-169-229-214-244.ets.berkeley.edu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
244.214.229.169.in-addr.arpa	name = fixed-169-229-214-244.ets.berkeley.edu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
165.22.101.134 attack
Jun 26 15:16:34 lnxmail61 sshd[17843]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.101.134
Jun 26 15:16:36 lnxmail61 sshd[17843]: Failed password for invalid user django from 165.22.101.134 port 48132 ssh2
Jun 26 15:19:57 lnxmail61 sshd[18284]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.101.134
2019-06-26 21:32:47
51.75.248.164 attackspambots
Triggered by Fail2Ban
2019-06-26 21:03:39
35.237.232.107 attackbots
RDP Brute-Force (Grieskirchen RZ1)
2019-06-26 20:44:15
112.115.103.10 attackbotsspam
23/tcp
[2019-06-26]1pkt
2019-06-26 20:45:04
212.83.183.155 attack
Invalid user admin from 212.83.183.155 port 35425
2019-06-26 20:57:54
193.105.134.96 attackbotsspam
Jun 26 06:35:22 ip-172-31-22-16 sshd\[20095\]: Invalid user admin from 193.105.134.96
Jun 26 06:36:02 ip-172-31-22-16 sshd\[20097\]: Invalid user support from 193.105.134.96
Jun 26 06:36:04 ip-172-31-22-16 sshd\[20101\]: Invalid user admin from 193.105.134.96
Jun 26 06:36:45 ip-172-31-22-16 sshd\[20106\]: Invalid user user from 193.105.134.96
Jun 26 06:37:36 ip-172-31-22-16 sshd\[20108\]: Invalid user admin from 193.105.134.96
2019-06-26 20:49:10
119.115.97.41 attackspam
5500/tcp
[2019-06-26]1pkt
2019-06-26 21:10:17
42.58.22.11 attackbotsspam
5500/tcp
[2019-06-26]1pkt
2019-06-26 20:51:14
185.137.111.123 attackbotsspam
2019-06-26T18:14:15.197942ns1.unifynetsol.net postfix/smtpd\[21587\]: warning: unknown\[185.137.111.123\]: SASL LOGIN authentication failed: authentication failure
2019-06-26T18:14:54.584678ns1.unifynetsol.net postfix/smtpd\[20011\]: warning: unknown\[185.137.111.123\]: SASL LOGIN authentication failed: authentication failure
2019-06-26T18:15:29.967739ns1.unifynetsol.net postfix/smtpd\[16950\]: warning: unknown\[185.137.111.123\]: SASL LOGIN authentication failed: authentication failure
2019-06-26T18:16:06.020671ns1.unifynetsol.net postfix/smtpd\[20013\]: warning: unknown\[185.137.111.123\]: SASL LOGIN authentication failed: authentication failure
2019-06-26T18:16:41.819109ns1.unifynetsol.net postfix/smtpd\[20013\]: warning: unknown\[185.137.111.123\]: SASL LOGIN authentication failed: authentication failure
2019-06-26 20:53:07
2607:5300:60:2bb::1 attack
wp brute-force
2019-06-26 20:51:33
60.169.114.213 attackbotsspam
Jun 26 05:24:05 mxgate1 postfix/postscreen[22819]: CONNECT from [60.169.114.213]:65192 to [176.31.12.44]:25
Jun 26 05:24:05 mxgate1 postfix/dnsblog[22820]: addr 60.169.114.213 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jun 26 05:24:05 mxgate1 postfix/dnsblog[22823]: addr 60.169.114.213 listed by domain zen.spamhaus.org as 127.0.0.11
Jun 26 05:24:05 mxgate1 postfix/dnsblog[22823]: addr 60.169.114.213 listed by domain zen.spamhaus.org as 127.0.0.4
Jun 26 05:24:05 mxgate1 postfix/dnsblog[22824]: addr 60.169.114.213 listed by domain cbl.abuseat.org as 127.0.0.2
Jun 26 05:24:05 mxgate1 postfix/dnsblog[22821]: addr 60.169.114.213 listed by domain b.barracudacentral.org as 127.0.0.2
Jun 26 05:24:11 mxgate1 postfix/postscreen[22819]: DNSBL rank 5 for [60.169.114.213]:65192
Jun x@x
Jun 26 05:26:07 mxgate1 postfix/postscreen[22819]: DISCONNECT [60.169.114.213]:65192


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=60.169.114.213
2019-06-26 20:49:45
78.187.78.193 attackbotsspam
Unauthorized connection attempt from IP address 78.187.78.193 on Port 445(SMB)
2019-06-26 21:22:11
1.170.28.52 attackspambots
37215/tcp
[2019-06-26]1pkt
2019-06-26 21:17:42
111.90.144.200 attackbotsspam
fail2ban honeypot
2019-06-26 21:17:03
149.56.129.68 attackspam
Jun 26 15:17:46 vps647732 sshd[4455]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.129.68
Jun 26 15:17:48 vps647732 sshd[4455]: Failed password for invalid user shoping from 149.56.129.68 port 38062 ssh2
...
2019-06-26 21:25:42

Recently Reported IPs

169.229.205.219 169.229.165.130 169.229.213.11 169.229.181.55
169.229.204.229 169.229.202.26 169.229.181.8 218.66.247.20
180.76.140.174 169.229.201.53 106.12.161.108 220.173.123.145
180.76.149.63 105.69.240.137 169.229.217.100 169.229.218.4
137.226.131.85 169.229.90.89 169.229.123.120 169.229.123.107