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

;; QUESTION SECTION:
;169.229.134.116.		IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jun 27 02:39:15 CST 2022
;; MSG SIZE  rcvd: 108
Host info
116.134.229.169.in-addr.arpa domain name pointer me103.me.berkeley.edu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
116.134.229.169.in-addr.arpa	name = me103.me.berkeley.edu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
68.183.150.254 attack
Aug 28 01:44:25 MK-Soft-VM4 sshd\[17370\]: Invalid user sinusbot from 68.183.150.254 port 34084
Aug 28 01:44:25 MK-Soft-VM4 sshd\[17370\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.150.254
Aug 28 01:44:27 MK-Soft-VM4 sshd\[17370\]: Failed password for invalid user sinusbot from 68.183.150.254 port 34084 ssh2
...
2019-08-28 10:05:40
51.15.212.48 attack
Aug 28 00:39:44 mail1 sshd\[28585\]: Invalid user named from 51.15.212.48 port 34844
Aug 28 00:39:44 mail1 sshd\[28585\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.212.48
Aug 28 00:39:46 mail1 sshd\[28585\]: Failed password for invalid user named from 51.15.212.48 port 34844 ssh2
Aug 28 00:54:26 mail1 sshd\[3094\]: Invalid user kibana from 51.15.212.48 port 56256
Aug 28 00:54:26 mail1 sshd\[3094\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.212.48
...
2019-08-28 09:57:47
118.24.6.219 attack
SSH/22 MH Probe, BF, Hack -
2019-08-28 10:20:03
113.23.231.90 attackspam
Aug 28 03:57:06 nextcloud sshd\[3152\]: Invalid user xd from 113.23.231.90
Aug 28 03:57:06 nextcloud sshd\[3152\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.23.231.90
Aug 28 03:57:08 nextcloud sshd\[3152\]: Failed password for invalid user xd from 113.23.231.90 port 35434 ssh2
...
2019-08-28 10:10:41
125.163.230.220 attackspambots
Aug 25 23:49:06 HOST sshd[21552]: reveeclipse mapping checking getaddrinfo for 220.subnet125-163-230.speedy.telkom.net.id [125.163.230.220] failed - POSSIBLE BREAK-IN ATTEMPT!
Aug 25 23:49:08 HOST sshd[21552]: Failed password for invalid user blessed from 125.163.230.220 port 58098 ssh2
Aug 25 23:49:08 HOST sshd[21552]: Received disconnect from 125.163.230.220: 11: Bye Bye [preauth]
Aug 26 00:01:55 HOST sshd[21886]: reveeclipse mapping checking getaddrinfo for 220.subnet125-163-230.speedy.telkom.net.id [125.163.230.220] failed - POSSIBLE BREAK-IN ATTEMPT!
Aug 26 00:01:57 HOST sshd[21886]: Failed password for invalid user semenov from 125.163.230.220 port 53164 ssh2
Aug 26 00:01:57 HOST sshd[21886]: Received disconnect from 125.163.230.220: 11: Bye Bye [preauth]
Aug 26 00:06:50 HOST sshd[22018]: reveeclipse mapping checking getaddrinfo for 220.subnet125-163-230.speedy.telkom.net.id [125.163.230.220] failed - POSSIBLE BREAK-IN ATTEMPT!
Aug 26 00:06:52 HOST sshd[22018]: Fa........
-------------------------------
2019-08-28 09:58:14
74.82.47.46 attackspambots
30005/tcp 11211/tcp 27017/tcp...
[2019-06-26/08-25]39pkt,19pt.(tcp),2pt.(udp)
2019-08-28 10:22:37
121.142.111.86 attackspambots
Aug 28 02:46:57 XXX sshd[20279]: Invalid user ofsaa from 121.142.111.86 port 48274
2019-08-28 10:04:41
34.243.33.89 attackspam
RDP Bruteforce
2019-08-28 10:11:43
107.170.198.115 attack
389/tcp 14373/tcp 3790/tcp...
[2019-06-26/08-27]74pkt,56pt.(tcp),4pt.(udp)
2019-08-28 10:06:05
113.237.128.232 attack
Unauthorised access (Aug 28) SRC=113.237.128.232 LEN=40 TTL=49 ID=12127 TCP DPT=8080 WINDOW=44155 SYN 
Unauthorised access (Aug 27) SRC=113.237.128.232 LEN=40 TTL=49 ID=13292 TCP DPT=8080 WINDOW=8511 SYN 
Unauthorised access (Aug 26) SRC=113.237.128.232 LEN=40 TTL=49 ID=36392 TCP DPT=8080 WINDOW=62926 SYN 
Unauthorised access (Aug 26) SRC=113.237.128.232 LEN=40 TTL=49 ID=30164 TCP DPT=8080 WINDOW=19987 SYN 
Unauthorised access (Aug 25) SRC=113.237.128.232 LEN=40 TTL=49 ID=25939 TCP DPT=8080 WINDOW=35304 SYN
2019-08-28 10:36:06
107.170.203.223 attackspam
5222/tcp 3790/tcp 34686/tcp...
[2019-06-26/08-26]64pkt,49pt.(tcp),5pt.(udp)
2019-08-28 10:07:20
186.28.100.45 attackspambots
BURG,WP GET /wp-login.php
2019-08-28 10:06:29
37.131.196.63 attackbots
37.131.196.63 has been banned for [spam]
...
2019-08-28 10:18:34
209.17.96.210 attackbotsspam
Brute force attack stopped by firewall
2019-08-28 10:34:50
196.234.145.245 attackbots
Attempted WordPress login: "GET /wp-login.php"
2019-08-28 10:27:34

Recently Reported IPs

169.229.133.225 169.229.134.103 169.229.133.245 169.229.99.133
169.229.101.73 169.229.101.12 169.229.120.170 169.229.120.167
169.229.120.180 169.229.120.191 51.91.78.31 169.229.135.205
169.229.135.242 169.229.72.49 169.229.72.209 169.229.73.76
169.229.73.88 169.229.73.133 169.229.73.178 169.229.102.48