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

;; QUESTION SECTION:
;169.229.18.148.			IN	A

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

;; Query time: 83 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 26 12:33:05 CST 2022
;; MSG SIZE  rcvd: 107
Host info
148.18.229.169.in-addr.arpa domain name pointer lb-ewh-libprod--ewdc2slb--631.lib.berkeley.edu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
148.18.229.169.in-addr.arpa	name = lb-ewh-libprod--ewdc2slb--631.lib.berkeley.edu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
178.128.56.22 attack
WordPress wp-login brute force :: 178.128.56.22 0.192 - [02/Jan/2020:14:54:05  0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1806 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2020-01-03 04:06:59
35.247.138.99 attackspam
xmlrpc attack
2020-01-03 04:06:38
185.142.236.35 attack
Unauthorized connection attempt detected from IP address 185.142.236.35 to port 1604
2020-01-03 04:01:15
118.89.240.188 attack
Unauthorized connection attempt detected from IP address 118.89.240.188 to port 22
2020-01-03 04:37:33
14.244.97.232 attackbots
TCP Port: 25      invalid blocked  abuseat-org also spamcop and zen-spamhaus           (455)
2020-01-03 04:02:36
37.49.231.102 attackspam
Automatic report - Banned IP Access
2020-01-03 04:12:40
104.244.75.12 attack
Jan  2 16:53:53 server2 sshd\[15823\]: Invalid user ubnt from 104.244.75.12
Jan  2 16:53:53 server2 sshd\[15825\]: Invalid user admin from 104.244.75.12
Jan  2 16:53:54 server2 sshd\[15827\]: User root from 104.244.75.12 not allowed because not listed in AllowUsers
Jan  2 16:53:54 server2 sshd\[15829\]: Invalid user 1234 from 104.244.75.12
Jan  2 16:53:54 server2 sshd\[15831\]: Invalid user usuario from 104.244.75.12
Jan  2 16:53:54 server2 sshd\[15833\]: Invalid user support from 104.244.75.12
2020-01-03 04:15:13
195.112.197.19 attackbots
spam
2020-01-03 04:39:31
123.142.108.122 attack
Jan  2 16:54:10 sd-53420 sshd\[28120\]: Invalid user usuario from 123.142.108.122
Jan  2 16:54:10 sd-53420 sshd\[28120\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.142.108.122
Jan  2 16:54:11 sd-53420 sshd\[28120\]: Failed password for invalid user usuario from 123.142.108.122 port 60476 ssh2
Jan  2 16:58:09 sd-53420 sshd\[29359\]: Invalid user tiger57a7 from 123.142.108.122
Jan  2 16:58:09 sd-53420 sshd\[29359\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.142.108.122
...
2020-01-03 04:01:49
107.137.148.165 attackbots
Jan  2 15:53:02 nextcloud sshd\[4608\]: Invalid user sakakihara from 107.137.148.165
Jan  2 15:53:02 nextcloud sshd\[4608\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.137.148.165
Jan  2 15:53:04 nextcloud sshd\[4608\]: Failed password for invalid user sakakihara from 107.137.148.165 port 54633 ssh2
...
2020-01-03 04:40:01
187.190.235.89 attackbots
Automatic report - Banned IP Access
2020-01-03 04:25:51
183.105.217.170 attackspam
2020-01-02T15:04:38.722792shield sshd\[18060\]: Invalid user P4sswOrd from 183.105.217.170 port 46705
2020-01-02T15:04:38.727231shield sshd\[18060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.105.217.170
2020-01-02T15:04:40.341855shield sshd\[18060\]: Failed password for invalid user P4sswOrd from 183.105.217.170 port 46705 ssh2
2020-01-02T15:08:24.617220shield sshd\[19158\]: Invalid user P@\$\$wort1q from 183.105.217.170 port 34100
2020-01-02T15:08:24.621708shield sshd\[19158\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.105.217.170
2020-01-03 04:24:36
51.91.136.174 attack
Jan  2 14:19:18 plusreed sshd[21473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.136.174  user=root
Jan  2 14:19:20 plusreed sshd[21473]: Failed password for root from 51.91.136.174 port 57512 ssh2
...
2020-01-03 04:12:59
112.85.42.173 attackbots
Jan  2 17:34:55 firewall sshd[21801]: Failed password for root from 112.85.42.173 port 17166 ssh2
Jan  2 17:34:55 firewall sshd[21801]: error: maximum authentication attempts exceeded for root from 112.85.42.173 port 17166 ssh2 [preauth]
Jan  2 17:34:55 firewall sshd[21801]: Disconnecting: Too many authentication failures [preauth]
...
2020-01-03 04:36:34
52.34.195.239 attackbots
01/02/2020-21:02:36.456375 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-03 04:08:55

Recently Reported IPs

169.229.18.170 137.226.218.47 169.229.54.240 169.229.40.164
137.226.221.83 169.229.41.194 137.226.224.218 137.226.223.67
137.226.227.122 137.226.223.130 137.226.225.82 137.226.128.252
137.226.128.253 137.226.129.0 137.226.129.2 137.226.129.7
222.141.14.191 222.141.21.255 169.229.160.223 169.229.170.140