169.229.49.138

Basic Info

City: unknown

Region: unknown

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

No discussion about this subnet yet..

Whois info:

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 169.229.49.138
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16710
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;169.229.49.138.			IN	A

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

;; Query time: 100 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 23 05:55:09 CST 2022
;; MSG SIZE  rcvd: 107

Host info

138.49.229.169.in-addr.arpa domain name pointer c38.millennium.berkeley.edu.

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
138.49.229.169.in-addr.arpa	name = c38.millennium.berkeley.edu.

Authoritative answers can be found from:

Related IP info:

Related comments:

IP	Type	Details	Datetime
78.128.112.114	attack	78.128.112.114 was recorded 127 times by 25 hosts attempting to connect to the following ports: 2314,1210,3164,1378,2511,2956,2725,1466,620,827,142,3110,930,3281,1354,615,2304,2189,521,2071,2839,2277,3248,883,462,2382,1711,1482,1311,2055,441,2399,2077,1879,2347,558,2934,1530,1607,987,1565,2116,1972,870,1507,754,2782,362,162,1497,2797,2393,1856,2315,2951,251,2389,613,16,2918,1333,2556,2935,2292,1024,902,188,2688,1993,2457,473,1681,1072,2614,1388,1326,2786,2475,3069,2719,595,1262,333,739,1123,1950,2632,17,1717,1952,2871,2669,3258,1775,2354,1173,1389,1511,69,3082,1099,1436,783,243,2969,3228,1147,1438,285,246,1658,950,1239,2581,938,1544,3217,954,1803,1057,1709,3203,1541,609. Incident counter (4h, 24h, all-time): 127, 902, 1710	2019-11-12 15:14:58
122.176.87.176	attackbots	Unauthorised access (Nov 12) SRC=122.176.87.176 LEN=52 TTL=118 ID=17112 DF TCP DPT=445 WINDOW=8192 SYN	2019-11-12 15:21:14
51.77.192.141	attack	Nov 12 12:28:28 gw1 sshd[7155]: Failed password for bin from 51.77.192.141 port 50418 ssh2 Nov 12 12:36:49 gw1 sshd[7246]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.192.141 ...	2019-11-12 15:54:00
222.186.180.9	attackbotsspam	Nov 12 08:28:24 ovpn sshd\[4128\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.9 user=root Nov 12 08:28:25 ovpn sshd\[4128\]: Failed password for root from 222.186.180.9 port 6248 ssh2 Nov 12 08:28:37 ovpn sshd\[4128\]: Failed password for root from 222.186.180.9 port 6248 ssh2 Nov 12 08:28:41 ovpn sshd\[4202\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.9 user=root Nov 12 08:28:43 ovpn sshd\[4202\]: Failed password for root from 222.186.180.9 port 11956 ssh2	2019-11-12 15:29:07
218.4.234.74	attackspambots	Nov 11 21:20:51 php1 sshd\[30018\]: Invalid user goppelt from 218.4.234.74 Nov 11 21:20:51 php1 sshd\[30018\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.4.234.74 Nov 11 21:20:53 php1 sshd\[30018\]: Failed password for invalid user goppelt from 218.4.234.74 port 2802 ssh2 Nov 11 21:26:50 php1 sshd\[30526\]: Invalid user nyx from 218.4.234.74 Nov 11 21:26:50 php1 sshd\[30526\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.4.234.74	2019-11-12 15:39:16
211.110.140.200	attackspam	Nov 12 08:09:02 vmd17057 sshd\[10980\]: Invalid user oracle4 from 211.110.140.200 port 48640 Nov 12 08:09:02 vmd17057 sshd\[10980\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.110.140.200 Nov 12 08:09:03 vmd17057 sshd\[10980\]: Failed password for invalid user oracle4 from 211.110.140.200 port 48640 ssh2 ...	2019-11-12 15:55:47
84.237.55.4	attackspam	[portscan] Port scan	2019-11-12 15:47:51
151.80.140.166	attack	SSH Brute-Force attacks	2019-11-12 15:32:34
175.212.62.83	attack	2019-11-12T01:17:19.0553511495-001 sshd\[54899\]: Invalid user bery from 175.212.62.83 port 52312 2019-11-12T01:17:19.0627211495-001 sshd\[54899\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.212.62.83 2019-11-12T01:17:21.2211311495-001 sshd\[54899\]: Failed password for invalid user bery from 175.212.62.83 port 52312 ssh2 2019-11-12T01:21:39.6473251495-001 sshd\[55014\]: Invalid user QWER4321g from 175.212.62.83 port 60250 2019-11-12T01:21:39.6550241495-001 sshd\[55014\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.212.62.83 2019-11-12T01:21:41.1716281495-001 sshd\[55014\]: Failed password for invalid user QWER4321g from 175.212.62.83 port 60250 ssh2 ...	2019-11-12 15:32:08
112.85.42.229	attack	F2B jail: sshd. Time: 2019-11-12 08:21:30, Reported by: VKReport	2019-11-12 15:33:59
160.153.156.47	attack	Automatic report - XMLRPC Attack	2019-11-12 15:52:58
13.73.23.71	attackspambots	RDP Bruteforce	2019-11-12 15:17:11
193.32.160.152	attack	Nov 12 07:32:32 relay postfix/smtpd\[27999\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.152\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.151\]\> Nov 12 07:32:32 relay postfix/smtpd\[27999\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.152\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.151\]\> Nov 12 07:32:32 relay postfix/smtpd\[27999\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.152\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.151\]\> Nov 12 07:32:32 relay postfix/smtpd\[27999\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.152\]: 554 5.7.1 \: Relay access denied\; from=\	2019-11-12 15:23:48
167.172.173.174	attack	Nov 11 21:09:42 php1 sshd\[28994\]: Invalid user patrisha from 167.172.173.174 Nov 11 21:09:42 php1 sshd\[28994\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.173.174 Nov 11 21:09:44 php1 sshd\[28994\]: Failed password for invalid user patrisha from 167.172.173.174 port 55582 ssh2 Nov 11 21:13:22 php1 sshd\[29337\]: Invalid user lydia from 167.172.173.174 Nov 11 21:13:22 php1 sshd\[29337\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.173.174	2019-11-12 15:19:53
193.32.163.44	attack	193.32.163.44 was recorded 15 times by 11 hosts attempting to connect to the following ports: 33062,33084,33086,33073,33052,33057,33070,33072,33076,33081,33055,33068,33093,33074. Incident counter (4h, 24h, all-time): 15, 108, 751	2019-11-12 15:51:55

Recently Reported IPs

169.229.10.64	169.229.48.90	169.229.39.11	137.226.32.29
169.229.27.160	180.76.232.2	123.125.71.139	169.229.29.6
169.229.39.75	169.229.9.108	137.226.51.113	137.226.40.78
137.226.60.31	137.226.71.11	180.76.8.0	75.139.203.210
137.226.232.147	137.226.236.246	89.248.165.189	137.226.238.239