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: None

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

;; QUESTION SECTION:
;169.229.214.253.		IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 16 04:16:59 CST 2022
;; MSG SIZE  rcvd: 108
Host info
253.214.229.169.in-addr.arpa domain name pointer fixed-169-229-214-253.ets.berkeley.edu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
213.195.124.127 attack
Jun 27 14:22:10 Ubuntu-1404-trusty-64-minimal sshd\[27055\]: Invalid user manager from 213.195.124.127
Jun 27 14:22:10 Ubuntu-1404-trusty-64-minimal sshd\[27055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.195.124.127
Jun 27 14:22:12 Ubuntu-1404-trusty-64-minimal sshd\[27055\]: Failed password for invalid user manager from 213.195.124.127 port 36482 ssh2
Jun 27 14:32:42 Ubuntu-1404-trusty-64-minimal sshd\[3056\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.195.124.127  user=root
Jun 27 14:32:44 Ubuntu-1404-trusty-64-minimal sshd\[3056\]: Failed password for root from 213.195.124.127 port 51312 ssh2
2020-06-28 03:59:19
83.239.38.2 attackbots
Jun 27 19:43:10 roki sshd[21977]: Invalid user course from 83.239.38.2
Jun 27 19:43:10 roki sshd[21977]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.239.38.2
Jun 27 19:43:11 roki sshd[21977]: Failed password for invalid user course from 83.239.38.2 port 50052 ssh2
Jun 27 19:44:55 roki sshd[22096]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.239.38.2  user=root
Jun 27 19:44:57 roki sshd[22096]: Failed password for root from 83.239.38.2 port 41664 ssh2
...
2020-06-28 04:02:01
177.73.119.83 attackspambots
port scan and connect, tcp 23 (telnet)
2020-06-28 04:25:41
178.32.163.249 attack
Jun 27 19:27:32 mail sshd[50341]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.32.163.249 
Jun 27 19:27:34 mail sshd[50341]: Failed password for invalid user hacked from 178.32.163.249 port 40946 ssh2
...
2020-06-28 04:08:08
60.169.73.80 attackspambots
firewall-block, port(s): 5901/tcp
2020-06-28 04:02:24
203.69.87.151 attack
Invalid user vbox from 203.69.87.151 port 22742
2020-06-28 04:21:51
195.97.75.174 attack
Jun 27 16:36:06 ns382633 sshd\[3319\]: Invalid user mon from 195.97.75.174 port 37834
Jun 27 16:36:06 ns382633 sshd\[3319\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.97.75.174
Jun 27 16:36:07 ns382633 sshd\[3319\]: Failed password for invalid user mon from 195.97.75.174 port 37834 ssh2
Jun 27 16:39:25 ns382633 sshd\[3623\]: Invalid user mon from 195.97.75.174 port 44620
Jun 27 16:39:25 ns382633 sshd\[3623\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.97.75.174
2020-06-28 04:03:23
192.35.169.25 attackbots
 TCP (SYN) 192.35.169.25:61373 -> port 445, len 44
2020-06-28 04:29:44
222.134.240.219 attackbotsspam
Jun 27 14:14:18 mellenthin postfix/smtpd[667]: warning: unknown[222.134.240.219]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 27 14:14:27 mellenthin postfix/smtpd[667]: warning: unknown[222.134.240.219]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-06-28 04:06:41
192.99.15.15 attackbotsspam
192.99.15.15 - - [27/Jun/2020:21:10:30 +0100] "POST /wp-login.php HTTP/1.1" 200 5871 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36"
192.99.15.15 - - [27/Jun/2020:21:11:46 +0100] "POST /wp-login.php HTTP/1.1" 200 5864 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36"
192.99.15.15 - - [27/Jun/2020:21:12:58 +0100] "POST /wp-login.php HTTP/1.1" 200 5864 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36"
...
2020-06-28 04:16:03
170.83.230.2 attackbotsspam
Jun 27 20:13:22 l02a sshd[32629]: Invalid user hvu from 170.83.230.2
Jun 27 20:13:22 l02a sshd[32629]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170-83-230-2.l2ktelecom.net.br 
Jun 27 20:13:22 l02a sshd[32629]: Invalid user hvu from 170.83.230.2
Jun 27 20:13:24 l02a sshd[32629]: Failed password for invalid user hvu from 170.83.230.2 port 39522 ssh2
2020-06-28 04:34:29
92.118.161.29 attackspambots
Honeypot hit.
2020-06-28 04:10:17
197.89.67.107 attack
1593260075 - 06/27/2020 14:14:35 Host: 197.89.67.107/197.89.67.107 Port: 445 TCP Blocked
2020-06-28 04:03:04
49.233.197.193 attackbotsspam
Jun 27 21:33:51 vpn01 sshd[921]: Failed password for root from 49.233.197.193 port 42124 ssh2
...
2020-06-28 04:27:47
148.227.227.66 attackbotsspam
Brute-force attempt banned
2020-06-28 04:33:57

Recently Reported IPs

169.229.214.57 169.229.215.17 169.229.215.134 169.229.215.34
169.229.215.141 180.76.121.114 180.76.121.214 180.76.121.217
180.76.122.41 9.146.170.165 169.229.251.6 169.229.218.137
169.229.213.155 169.229.217.163 169.229.247.59 169.229.241.150
169.229.218.109 169.229.218.117 169.229.219.1 169.229.219.16