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

;; QUESTION SECTION:
;169.229.153.139.		IN	A

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

;; Query time: 93 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jun 14 05:48:58 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 139.153.229.169.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 139.153.229.169.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
84.17.51.12 attack
As always with datacamp
2020-03-08 06:01:56
222.186.175.220 attack
Mar  7 23:19:43 serwer sshd\[3031\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.220  user=root
Mar  7 23:19:45 serwer sshd\[3031\]: Failed password for root from 222.186.175.220 port 22852 ssh2
Mar  7 23:19:48 serwer sshd\[3031\]: Failed password for root from 222.186.175.220 port 22852 ssh2
...
2020-03-08 06:23:57
220.135.40.78 attackbots
firewall-block, port(s): 81/tcp
2020-03-08 06:26:48
3.0.223.188 attack
WordPress brute force
2020-03-08 06:07:15
36.68.104.224 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-08 05:50:14
200.109.38.9 attack
1583619036 - 03/07/2020 23:10:36 Host: 200.109.38.9/200.109.38.9 Port: 445 TCP Blocked
2020-03-08 06:18:08
183.80.230.208 attackbotsspam
Sat Mar  7 15:10:44 2020 - Child process 400129 handling connection
Sat Mar  7 15:10:44 2020 - New connection from: 183.80.230.208:54663
Sat Mar  7 15:10:44 2020 - Sending data to client: [Login: ]
Sat Mar  7 15:11:15 2020 - Child aborting
Sat Mar  7 15:11:15 2020 - Reporting IP address: 183.80.230.208 - mflag: 0
2020-03-08 06:29:51
222.186.175.148 attackspambots
Mar  7 23:22:22 SilenceServices sshd[22693]: Failed password for root from 222.186.175.148 port 4958 ssh2
Mar  7 23:22:35 SilenceServices sshd[22693]: error: maximum authentication attempts exceeded for root from 222.186.175.148 port 4958 ssh2 [preauth]
Mar  7 23:23:01 SilenceServices sshd[30209]: Failed password for root from 222.186.175.148 port 19304 ssh2
2020-03-08 06:25:22
60.190.248.11 attackbots
60.190.248.11 was recorded 31 times by 1 hosts attempting to connect to the following ports: 631,808,873,902,21,23,25,1720,37,1723,1911,1962,110,3306,119,3460,5060,5353,177,5432,179,5489,389,5900,6001,445,6379,502,8000,515. Incident counter (4h, 24h, all-time): 31, 31, 242
2020-03-08 06:16:34
207.154.193.178 attackspam
Mar  7 22:54:26 ns382633 sshd\[23923\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.193.178  user=root
Mar  7 22:54:28 ns382633 sshd\[23923\]: Failed password for root from 207.154.193.178 port 41754 ssh2
Mar  7 23:06:44 ns382633 sshd\[26269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.193.178  user=root
Mar  7 23:06:46 ns382633 sshd\[26269\]: Failed password for root from 207.154.193.178 port 57536 ssh2
Mar  7 23:10:49 ns382633 sshd\[27060\]: Invalid user apache from 207.154.193.178 port 55910
Mar  7 23:10:49 ns382633 sshd\[27060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.193.178
2020-03-08 06:12:34
45.95.168.111 attack
suspicious action Sat, 07 Mar 2020 18:00:39 -0300
2020-03-08 05:58:09
193.112.173.211 attackspam
Mar  7 23:05:08 sd-53420 sshd\[31972\]: User root from 193.112.173.211 not allowed because none of user's groups are listed in AllowGroups
Mar  7 23:05:08 sd-53420 sshd\[31972\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.173.211  user=root
Mar  7 23:05:09 sd-53420 sshd\[31972\]: Failed password for invalid user root from 193.112.173.211 port 49822 ssh2
Mar  7 23:10:35 sd-53420 sshd\[32537\]: User root from 193.112.173.211 not allowed because none of user's groups are listed in AllowGroups
Mar  7 23:10:35 sd-53420 sshd\[32537\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.173.211  user=root
...
2020-03-08 06:19:22
36.82.99.191 attackspambots
1583587567 - 03/07/2020 14:26:07 Host: 36.82.99.191/36.82.99.191 Port: 445 TCP Blocked
2020-03-08 06:10:01
49.88.112.67 attackspam
Mar  7 23:09:29 v22018053744266470 sshd[1389]: Failed password for root from 49.88.112.67 port 55193 ssh2
Mar  7 23:10:38 v22018053744266470 sshd[1465]: Failed password for root from 49.88.112.67 port 33146 ssh2
Mar  7 23:10:41 v22018053744266470 sshd[1465]: Failed password for root from 49.88.112.67 port 33146 ssh2
...
2020-03-08 06:17:18
191.26.228.96 attack
suspicious action Sat, 07 Mar 2020 10:26:20 -0300
2020-03-08 06:00:58

Recently Reported IPs

169.229.152.210 169.229.157.67 169.229.156.224 169.229.157.35
185.108.171.91 169.229.156.157 169.229.162.13 169.229.158.112
169.229.161.211 169.229.163.24 169.229.165.91 169.229.158.148
169.229.163.245 169.229.164.101 169.229.164.42 169.229.158.160
169.229.162.213 169.229.140.155 169.229.159.108 169.229.155.83