IP: 169.229.3.91 United States Location: Oakland, California, United States
City:
Oakland
Region:
California
Country:
United States
Postal Code:
94607
Latitude:
37.8084
Longitude:
-122.2846
NetRange: 169.229.0.0 - 169.233.255.255
CIDR: 169.232.0.0/15, 169.230.0.0/15, 169.229.0.0/16
NetName: UCSD-NET-169-228
NetHandle: NET-169-229-0-0-1
Parent: NET169 (NET-169-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: University of California - Office of the President (UCOP-Z)
RegDate: 1995-08-04
Updated: 2021-10-05
Ref: https://rdap.arin.net/registry/ip/169.229.0.0

OrgName: University of California - Office of the President
OrgId: UCOP-Z
Address: Information Technology Services
Address: 1111 Franklin Street
City: Oakland
StateProv: CA
PostalCode: 94607
Country: US
RegDate: 2018-11-01
Updated: 2018-11-01
Ref: https://rdap.arin.net/registry/entity/UCOP-Z

OrgAbuseHandle: NETWO575-ARIN
OrgAbuseName: Network Operations
OrgAbusePhone: +1-510-987-0363
OrgAbuseEmail: noc@ucop.edu
OrgAbuseRef: https://rdap.arin.net/registry/entity/NETWO575-ARIN

OrgTechHandle: NETWO575-ARIN
OrgTechName: Network Operations
OrgTechPhone: +1-510-987-0363
OrgTechEmail: noc@ucop.edu
OrgTechRef: https://rdap.arin.net/registry/entity/NETWO575-ARIN

RTechHandle: NETWO576-ARIN
RTechName: Network Operations
RTechPhone: +1-510-987-0363
RTechEmail: noc@ucop.edu
RTechRef: https://rdap.arin.net/registry/entity/NETWO576-ARIN

RAbuseHandle: NETWO577-ARIN
RAbuseName: Network Operations
RAbusePhone: +1-510-987-0534
RAbuseEmail: abuse@ucop.edu
RAbuseRef: https://rdap.arin.net/registry/entity/NETWO577-ARIN

RNOCHandle: NETWO575-ARIN
RNOCName: Network Operations
RNOCPhone: +1-510-987-0363
RNOCEmail: noc@ucop.edu
RNOCRef: https://rdap.arin.net/registry/entity/NETWO575-ARIN

RTechHandle: UD14-ORG-ARIN
RTechName: UCNet DNS Administrator
RTechPhone: +1-510-893-9242
RTechEmail: dns-admin@ucnet.net
RTechRef: https://rdap.arin.net/registry/entity/UD14-ORG-ARIN

NetRange: 169.229.0.0 - 169.229.255.255
CIDR: 169.229.0.0/16
NetName: ISTDATA
NetHandle: NET-169-229-0-0-2
Parent: UCSD-NET-169-228 (NET-169-229-0-0-1)
NetType: Reassigned
OriginAS: AS25
Organization: University of California at Berkeley (UCAB-1)
RegDate: 1996-05-01
Updated: 2023-06-15
Comment: DMCA Designated Agent is dmca@berkeley.edu
Ref: https://rdap.arin.net/registry/ip/169.229.0.0

OrgName: University of California at Berkeley
OrgId: UCAB-1
Address: IST - Telecommunications
Address: ATTN Network Services and Operations
Address: 2850 Telegraph Ave
Address: NOTE See Comment for DMCA INFO
City: Berkeley
StateProv: CA
PostalCode: 94705
Country: US
RegDate: 1991-03-06
Updated: 2023-06-12
Comment: DMCA Designated Agent is dmca@berkeley.edu
Ref: https://rdap.arin.net/registry/entity/UCAB-1

OrgAbuseHandle: UCBSE-ARIN
OrgAbuseName: UCB-SECURIT-ARIN
OrgAbusePhone: +1-510-664-9000
OrgAbuseEmail: abuse@security.berkeley.edu
OrgAbuseRef: https://rdap.arin.net/registry/entity/UCBSE-ARIN

OrgNOCHandle: UCB-NOC-ARIN
OrgNOCName: IST Communication and Network Services
OrgNOCPhone: +1-510-664-9000
OrgNOCEmail: noc@berkeley.edu
OrgNOCRef: https://rdap.arin.net/registry/entity/UCB-NOC-ARIN

OrgTechHandle: UCB-NOC-ARIN
OrgTechName: IST Communication and Network Services
OrgTechPhone: +1-510-664-9000
OrgTechEmail: noc@berkeley.edu
OrgTechRef: https://rdap.arin.net/registry/entity/UCB-NOC-ARIN

RTechHandle: UCB-NOC-ARIN
RTechName: IST Communication and Network Services
RTechPhone: +1-510-664-9000
RTechEmail: noc@berkeley.edu
RTechRef: https://rdap.arin.net/registry/entity/UCB-NOC-ARIN
DNS BlackList results:
Most recent complaints on 169.229.3.91
Complaint by who :

Ip 169.229.3.91 are trying to hack my server

Reported on: 26th, Dec. 2014
Complaint by Anonymous :

Attempted database hack

Reported on: 21st, Jan. 2016
Complaint by WXCC :

Looks like a hack attempt coming from 169.229.3.91.

Reported on: 25th, Jan. 2016
Complaint by TheDeamon :

Exploit attempt!!! [Thu Feb 04 08:29:16.888853 2016] [core:error] [pid 14051] [client 169.229.3.91:52806] AH00135: Invalid method in request n\x9fB\xb5\x91`\xbdJ>\x85j\xdd\xbf\xf5\xa7w\x15h\xef\xa6\xe0\xaf*\xa65f\xa9\x15\xcd|O\xa1\xf4,D@\xb2D1\xd4\x1c#

Reported on: 7th, Feb. 2016
Complaint by dadude :

This IP tried the following hack attempt at my server: 169.229.3.91 - - [18/Feb/2016:14:03:27 +0200] "\xD1p\xB9\x8D.\x8FFr\xE1r\x1B\xA32\xDDf\xAF\x85\xA6'Dld\xD1\xEDi(\x93\xDE\x9FDeZ\xECryO>3AS\xBB\x19\xD7;\xB9k\x0C\xA0D\xBEN\xCB\x87+\xDC\x95(\xA6\xA7 \x8EEg&\xC2" 400 172 "-" "-"

Reported on: 18th, Feb. 2016
Complaint by cosmc space monkey :

same shellcode as above in the request

Reported on: 24th, Feb. 2016
Complaint by roodkapje9 :

I have blocked this ip, get lost. [Fri Mar 04 11:53:12.205409 2016] [core:error] [pid 1263] [client 169.229.3.91:37088] AH00135: Invalid method in request \xc6^

Reported on: 4th, Mar. 2016
Complaint by theOC :

snort detects a "http_inspect: UNESCAPED SPACE IN HTTP URI" coming from this IP address

Reported on: 9th, Mar. 2016
Complaint by paderEpiktet :

Strange request from [core:error] [pid 1485] [client 169.229.3.91:58357] AH00126: Invalid URI in request \xc1\xddd\xf3\x86e\xa3\xc5\xe1.\xde\xf2>"\x9b\x0c\x8e|O\x9c\x01wYg\xc0)\xe8\x9c\x8dA\xa7M\xbb\xc9\xe6\x83\x82F\xdf'M=8\xae\xbaP\xb1\xff\xcfB\x12\xb5\xd6\xea\x11\x9afM\x14&

Reported on: 21st, Mar. 2016
Complaint by Anonymous :

This showed up in my Apache error log... [Mon Mar 21 06:33:57 2016] [error] [client 169.229.3.91] Invalid URI in request P\x89*\x1d]\xfe\x9e\xe0"\x1f\xc4\xec\xafv\xd5\xe211\xa9\xa7\xcc\xb9?\xd7\xddI\xe9~w\xd2m-\x12U:\xa0_j&\t\xf1\xf2@\xd4"\xbb\xbcS\xdf\x9cp\xd8,<:M\x8d\bCI\x01

Reported on: 21st, Mar. 2016
Complaint by G A :

Same attack at my server.. =/

Reported on: 1st, May. 2016
Complaint by christophe :

169.229.3.91 05 May 2016 Q\x12,\xa4\xfe\x0c\xa3\x11\xd6T*\xe3\xae\xed\xd3 169.229.3.91 06 May 2016 \x85~=\x0cz\x81\xc2\xf3\xfdz\x18 169.229.3.91 10 May 2016 v\xee\xc7\xee\x89\x118\x11\xdc\x8f\xdd\xedXR"\xa7\x7f\xf9I\x1a/\x9a\x12\x9bC\xe8\xca\xf1X\x83\x9f\xcc\xed5i6n\xbb\xac\x12\x85U4q\x91\x80\xa0qR\x1f?kmQ\xbeL\x88(\x14c\xa4 169.229.3.91 24 May 2016 \x8es\x12\xafq\x8c\xedP\xe7$^\x1d?,\x1b\xe1\xd8\x92\x98\x93\x05\x1e~\x0c\xa9K\xdf\xf7^\xc0 169.229.3.91 25 Apr 2016 H\xa1; 169.229.3.91 25 May 2016 \x02\x05H6\x8d\xce6f\xc9\x16\xefu\xfd\xfa\xb7\xc9c\xac\xb8V\xc4\xb9 169.229.3.91 30 Apr 2016 \x99s\xb1\xb6f\x8cNI\xe7bm3\x92\x87\xee%wa\xfa

Reported on: 26th, May. 2016
Complaint by tatorface :

access log: 169.229.3.91 - - [10/Jul/2016:07:04:47 -0500] "'\xf6\xd7\xcf\xd8\t(0\xec\xaf\x9fO\xdf@\xabV\xe6\xacp$J\xaa\xf8\\\x867\xf1\x1eOyd\xf7/\x16\x86\xd6\xf0\xb0\x8f\x06j\x88\xccuT\\\xdeN" 400 314 "-" "-" error log: [Sun Jul 10 07:04:47 2016] [error] [client 169.229.3.91] Invalid URI in request '\xf6\xd7\xcf\xd8\t(0\xec\xaf\x9fO\xdf@\xabV\xe6\xacp$J\xaa\xf8\\\x867\xf1\x1eOyd\xf7/\x16\x86\xd6\xf0\xb0\x8f\x06j\x88\xccuT\\\xdeN

Reported on: 11th, Jul. 2016
Complaint by Crypter :

this ip 169.229.3.91 was hitting my system's all open ports. It was a hacking attempt..

Reported on: 9th, Aug. 2016
Complaint by None :

Found this in my Nginx access.log few hours after creating a DynDNS hostname : 169.229.3.91 - - [10/Nov/2016:11:25:52 +0000] "\xDD\xB63t\x22I\xCC\x8Bmg\xE8\xBA+\xBD\xAF\x9D\x93\x0F%\xF8{\x8D\xD5P\xC0\xE7KYSR\xE8/o\xFB\x07\xD1\xEB\x83\xEF\xDF]\xA4J\xBE\xCC\x1F9c\x1E\x93B\x5C1\xA5\xDAl4\xB5\x8D\xD4\xA4\xF0\xEC\xAE" 400 166 "-" "-"

Reported on: 10th, Nov. 2016

Please help us keep Internet safer and cleaner by leaving a descriptive comment about 169.229.3.91 IP address


DNSBL* - is a list of IP addresses published through the Internet Domain Name Service (DNS) either as a zone file that can be used by DNS server software, or as a live DNS zone that can be queried in real-time. DNSBLs are most often used to publish the addresses of computers or networks linked to spamming; most mail server software can be configured to reject or flag messages which have been sent from a site listed on one or more such lists.

WHOIS** - is a query/response protocol that is widely used for querying databases in order to determine the registrant or assignee of Internet resources, such as a domain name, an IP address block, or an autonomous system number. WHOIS lookups were traditionally performed with a command line interface application, and network administrators predominantly still use this method, but many simplified web-based tools exist. WHOIS services are typically communicated using the Transmission Control Protocol (TCP). Servers listen to requests on the well-known port number 43.

** Approximate Geographic Location - This is NOT the exact geographical location of the person/organization with the given IP address. However, this should still give you a good idea about the area/region where this person/orgranization is located.