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

;; QUESTION SECTION:
;169.229.12.201.			IN	A

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

;; Query time: 84 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jun 13 17:28:42 CST 2022
;; MSG SIZE  rcvd: 107
Host info
201.12.229.169.in-addr.arpa domain name pointer bdsn-vpn-gw-old.geo.berkeley.edu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
201.12.229.169.in-addr.arpa	name = bdsn-vpn-gw-old.geo.berkeley.edu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
114.236.204.63 attackspam
Unauthorised access (Sep  2) SRC=114.236.204.63 LEN=40 TOS=0x10 PREC=0x40 TTL=49 ID=2538 TCP DPT=8080 WINDOW=53212 SYN 
Unauthorised access (Sep  2) SRC=114.236.204.63 LEN=40 TOS=0x10 PREC=0x40 TTL=49 ID=1144 TCP DPT=8080 WINDOW=53212 SYN 
Unauthorised access (Sep  2) SRC=114.236.204.63 LEN=40 TOS=0x10 PREC=0x40 TTL=49 ID=49880 TCP DPT=8080 WINDOW=62356 SYN
2019-09-03 04:59:15
61.227.232.72 attack
Honeypot attack, port: 23, PTR: 61-227-232-72.dynamic-ip.hinet.net.
2019-09-03 05:05:24
106.13.5.170 attackbotsspam
Sep  2 23:02:08 v22019058497090703 sshd[5539]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.5.170
Sep  2 23:02:10 v22019058497090703 sshd[5539]: Failed password for invalid user vbox from 106.13.5.170 port 60200 ssh2
Sep  2 23:06:47 v22019058497090703 sshd[5933]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.5.170
...
2019-09-03 05:12:02
94.78.244.8 attackbots
23/tcp
[2019-09-02]1pkt
2019-09-03 05:02:52
142.93.15.1 attack
Sep  2 08:07:33 hpm sshd\[15797\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.15.1  user=root
Sep  2 08:07:35 hpm sshd\[15797\]: Failed password for root from 142.93.15.1 port 37700 ssh2
Sep  2 08:11:37 hpm sshd\[16224\]: Invalid user skeng from 142.93.15.1
Sep  2 08:11:37 hpm sshd\[16224\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.15.1
Sep  2 08:11:38 hpm sshd\[16224\]: Failed password for invalid user skeng from 142.93.15.1 port 54434 ssh2
2019-09-03 04:35:25
167.71.217.70 attackbots
Sep  2 20:31:28 MK-Soft-VM5 sshd\[4508\]: Invalid user sysadmin from 167.71.217.70 port 34152
Sep  2 20:31:28 MK-Soft-VM5 sshd\[4508\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.217.70
Sep  2 20:31:30 MK-Soft-VM5 sshd\[4508\]: Failed password for invalid user sysadmin from 167.71.217.70 port 34152 ssh2
...
2019-09-03 05:08:09
134.209.145.110 attackspambots
Sep  2 09:40:19 hiderm sshd\[19016\]: Invalid user fabien from 134.209.145.110
Sep  2 09:40:19 hiderm sshd\[19016\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.145.110
Sep  2 09:40:22 hiderm sshd\[19016\]: Failed password for invalid user fabien from 134.209.145.110 port 38652 ssh2
Sep  2 09:45:05 hiderm sshd\[19394\]: Invalid user berit from 134.209.145.110
Sep  2 09:45:05 hiderm sshd\[19394\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.145.110
2019-09-03 05:09:57
128.199.78.191 attackbots
Sep  2 06:34:45 web1 sshd\[9237\]: Invalid user venkat from 128.199.78.191
Sep  2 06:34:45 web1 sshd\[9237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.78.191
Sep  2 06:34:47 web1 sshd\[9237\]: Failed password for invalid user venkat from 128.199.78.191 port 40667 ssh2
Sep  2 06:41:05 web1 sshd\[9918\]: Invalid user bonec from 128.199.78.191
Sep  2 06:41:05 web1 sshd\[9918\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.78.191
2019-09-03 04:30:01
41.224.247.251 attackbots
445/tcp
[2019-09-02]1pkt
2019-09-03 04:57:05
45.12.220.233 attack
Sep  2 22:07:04 rotator sshd\[14777\]: Invalid user apc from 45.12.220.233Sep  2 22:07:06 rotator sshd\[14777\]: Failed password for invalid user apc from 45.12.220.233 port 35169 ssh2Sep  2 22:07:09 rotator sshd\[14781\]: Failed password for root from 45.12.220.233 port 35617 ssh2Sep  2 22:07:09 rotator sshd\[14783\]: Invalid user admin from 45.12.220.233Sep  2 22:07:11 rotator sshd\[14783\]: Failed password for invalid user admin from 45.12.220.233 port 36149 ssh2Sep  2 22:07:14 rotator sshd\[14797\]: Failed password for root from 45.12.220.233 port 36537 ssh2Sep  2 22:07:14 rotator sshd\[14799\]: Invalid user oper from 45.12.220.233
...
2019-09-03 04:45:35
1.173.81.221 attackspambots
23/tcp
[2019-09-02]1pkt
2019-09-03 04:31:01
123.13.24.217 attackspam
Sep  2 15:04:06 ghostname-secure sshd[11924]: reveeclipse mapping checking getaddrinfo for hn.kd.ny.adsl [123.13.24.217] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep  2 15:04:06 ghostname-secure sshd[11924]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.13.24.217  user=r.r
Sep  2 15:04:08 ghostname-secure sshd[11924]: Failed password for r.r from 123.13.24.217 port 53348 ssh2
Sep  2 15:04:11 ghostname-secure sshd[11924]: Failed password for r.r from 123.13.24.217 port 53348 ssh2
Sep  2 15:04:13 ghostname-secure sshd[11924]: Failed password for r.r from 123.13.24.217 port 53348 ssh2
Sep  2 15:04:16 ghostname-secure sshd[11924]: Failed password for r.r from 123.13.24.217 port 53348 ssh2
Sep  2 15:04:19 ghostname-secure sshd[11924]: Failed password for r.r from 123.13.24.217 port 53348 ssh2
Sep  2 15:04:21 ghostname-secure sshd[11924]: Failed password for r.r from 123.13.24.217 port 53348 ssh2
Sep  2 15:04:21 ghostname-secure sshd[1........
-------------------------------
2019-09-03 05:03:12
207.237.235.99 attack
Sep  2 16:15:09 ny01 sshd[7543]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.237.235.99
Sep  2 16:15:09 ny01 sshd[7544]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.237.235.99
Sep  2 16:15:11 ny01 sshd[7543]: Failed password for invalid user pi from 207.237.235.99 port 56086 ssh2
2019-09-03 04:31:55
148.66.135.178 attackspam
Sep  2 21:48:51 MainVPS sshd[723]: Invalid user vpn from 148.66.135.178 port 48284
Sep  2 21:48:51 MainVPS sshd[723]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.135.178
Sep  2 21:48:51 MainVPS sshd[723]: Invalid user vpn from 148.66.135.178 port 48284
Sep  2 21:48:54 MainVPS sshd[723]: Failed password for invalid user vpn from 148.66.135.178 port 48284 ssh2
Sep  2 21:56:37 MainVPS sshd[1439]: Invalid user julie from 148.66.135.178 port 36322
...
2019-09-03 05:01:28
54.37.225.179 attackbots
SSH Brute-Force reported by Fail2Ban
2019-09-03 04:40:22

Recently Reported IPs

137.226.199.134 169.229.7.2 169.229.16.228 190.120.186.30
169.229.4.73 169.229.14.82 169.229.16.181 169.229.11.231
137.226.206.36 137.226.201.165 137.226.217.166 137.226.202.200
137.226.217.19 137.226.199.25 169.229.101.111 169.229.42.131
137.226.254.69 169.229.40.52 169.229.44.21 169.229.7.165