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: San Jose

Region: California

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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#



# start

NetRange:       3.0.0.0 - 3.127.255.255
CIDR:           3.0.0.0/9
NetName:        AT-88-Z
NetHandle:      NET-3-0-0-0-1
Parent:         NET3 (NET-3-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Amazon Technologies Inc. (AT-88-Z)
RegDate:        2017-12-20
Updated:        2022-05-18
Ref:            https://rdap.arin.net/registry/ip/3.0.0.0



OrgName:        Amazon Technologies Inc.
OrgId:          AT-88-Z
Address:        410 Terry Ave N.
City:           Seattle
StateProv:      WA
PostalCode:     98109
Country:        US
RegDate:        2011-12-08
Updated:        2024-01-24
Comment:        All abuse reports MUST include:
Comment:        * src IP
Comment:        * dest IP (your IP)
Comment:        * dest port
Comment:        * Accurate date/timestamp and timezone of activity
Comment:        * Intensity/frequency (short log extracts)
Comment:        * Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref:            https://rdap.arin.net/registry/entity/AT-88-Z


OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName:   IP Routing
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/IPROU3-ARIN

OrgRoutingHandle: ARMP-ARIN
OrgRoutingName:   AWS RPKI Management POC
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-rpki-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/ARMP-ARIN

OrgNOCHandle: AANO1-ARIN
OrgNOCName:   Amazon AWS Network Operations
OrgNOCPhone:  +1-206-555-0000 
OrgNOCEmail:  amzn-noc-contact@amazon.com
OrgNOCRef:    https://rdap.arin.net/registry/entity/AANO1-ARIN

OrgAbuseHandle: AEA8-ARIN
OrgAbuseName:   Amazon EC2 Abuse
OrgAbusePhone:  +1-206-555-0000 
OrgAbuseEmail:  trustandsafety@support.aws.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/AEA8-ARIN

OrgTechHandle: ANO24-ARIN
OrgTechName:   Amazon EC2 Network Operations
OrgTechPhone:  +1-206-555-0000 
OrgTechEmail:  amzn-noc-contact@amazon.com
OrgTechRef:    https://rdap.arin.net/registry/entity/ANO24-ARIN

# end


# start

NetRange:       3.101.0.0 - 3.101.255.255
CIDR:           3.101.0.0/16
NetName:        AMAZON-SFO
NetHandle:      NET-3-101-0-0-1
Parent:         AT-88-Z (NET-3-0-0-0-1)
NetType:        Reallocated
OriginAS:       
Organization:   Amazon.com, Inc. (AMAZO-48)
RegDate:        2020-01-30
Updated:        2020-01-30
Ref:            https://rdap.arin.net/registry/ip/3.101.0.0


OrgName:        Amazon.com, Inc.
OrgId:          AMAZO-48
Address:        1200 12th Ave South
City:           Seattle
StateProv:      WA
PostalCode:     98144
Country:        US
RegDate:        2011-08-11
Updated:        2021-07-22
Comment:        The activity you have detected originates from a dynamic hosting environment. 
Comment:        For fastest response, please submit abuse reports at http://aws-portal.amazon.com/gp/aws/html-forms-controller/contactus/AWSAbuse 
Comment:        For more information regarding EC2 see: 
Comment:        http://ec2.amazonaws.com/ 
Comment:        All reports MUST include: 
Comment:        * src IP 
Comment:        * dest IP (your IP) 
Comment:        * dest port 
Comment:        * Accurate date/timestamp and timezone of activity 
Comment:        * Intensity/frequency (short log extracts) 
Comment:        * Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref:            https://rdap.arin.net/registry/entity/AMAZO-48


OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName:   IP Routing
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/IPROU3-ARIN

OrgNOCHandle: AANO1-ARIN
OrgNOCName:   Amazon AWS Network Operations
OrgNOCPhone:  +1-206-555-0000 
OrgNOCEmail:  amzn-noc-contact@amazon.com
OrgNOCRef:    https://rdap.arin.net/registry/entity/AANO1-ARIN

OrgRoutingHandle: ARMP-ARIN
OrgRoutingName:   AWS RPKI Management POC
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-rpki-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/ARMP-ARIN

OrgAbuseHandle: AEA8-ARIN
OrgAbuseName:   Amazon EC2 Abuse
OrgAbusePhone:  +1-206-555-0000 
OrgAbuseEmail:  trustandsafety@support.aws.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/AEA8-ARIN

OrgTechHandle: ANO24-ARIN
OrgTechName:   Amazon EC2 Network Operations
OrgTechPhone:  +1-206-555-0000 
OrgTechEmail:  amzn-noc-contact@amazon.com
OrgTechRef:    https://rdap.arin.net/registry/entity/ANO24-ARIN

# end



#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 3.101.22.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27121
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;3.101.22.12.			IN	A

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

;; Query time: 29 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 01 09:30:49 CST 2026
;; MSG SIZE  rcvd: 104
Host info
12.22.101.3.in-addr.arpa domain name pointer ec2-3-101-22-12.us-west-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.22.101.3.in-addr.arpa	name = ec2-3-101-22-12.us-west-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
181.48.116.50 attack
Dec 26 14:38:08 marvibiene sshd[54987]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.116.50  user=root
Dec 26 14:38:10 marvibiene sshd[54987]: Failed password for root from 181.48.116.50 port 47910 ssh2
Dec 26 14:51:39 marvibiene sshd[55279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.116.50  user=root
Dec 26 14:51:41 marvibiene sshd[55279]: Failed password for root from 181.48.116.50 port 40322 ssh2
...
2019-12-27 02:35:29
112.29.140.225 attackbots
$f2bV_matches
2019-12-27 02:35:09
145.239.95.83 attackspambots
2019-12-26T17:22:54.742538abusebot-2.cloudsearch.cf sshd[18173]: Invalid user http from 145.239.95.83 port 59960
2019-12-26T17:22:54.748462abusebot-2.cloudsearch.cf sshd[18173]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.ip-145-239-95.eu
2019-12-26T17:22:54.742538abusebot-2.cloudsearch.cf sshd[18173]: Invalid user http from 145.239.95.83 port 59960
2019-12-26T17:22:56.460967abusebot-2.cloudsearch.cf sshd[18173]: Failed password for invalid user http from 145.239.95.83 port 59960 ssh2
2019-12-26T17:24:49.886987abusebot-2.cloudsearch.cf sshd[18177]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.ip-145-239-95.eu  user=root
2019-12-26T17:24:52.018293abusebot-2.cloudsearch.cf sshd[18177]: Failed password for root from 145.239.95.83 port 52366 ssh2
2019-12-26T17:26:50.066706abusebot-2.cloudsearch.cf sshd[18181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=8
...
2019-12-27 02:32:54
103.84.108.234 attack
[ 🇳🇱 ] REQUEST: /l.php
2019-12-27 02:47:39
106.13.86.18 attackspam
$f2bV_matches
2019-12-27 02:40:48
61.163.128.231 attackspambots
Fail2Ban Ban Triggered
2019-12-27 02:44:57
197.44.197.143 attackbotsspam
port scan and connect, tcp 23 (telnet)
2019-12-27 03:01:44
132.232.52.60 attack
Invalid user atlas from 132.232.52.60 port 48394
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.52.60
Failed password for invalid user atlas from 132.232.52.60 port 48394 ssh2
Invalid user webadmin from 132.232.52.60 port 51496
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.52.60
2019-12-27 02:35:42
206.217.139.200 attackbotsspam
(From sandy157@hotmail.com) Аdult free dating sites in east lоndon: https://vae.me/95Cf
2019-12-27 02:59:37
209.85.220.41 attackspam
This IP address is linked to major fraud and crimes of Bitcoin theft, expeditehackers@ gmail.com is ran from this IP address, so is getbackfunds@gmail.com who pose and impersonate themselves as Bitcoin theft recovery agents. They will prey on and steal from folk for a second time who have come to them looking for help with previous instances of Bitcoin theft. Both sites www.expeditetools.com and www.getbackfunds.org will also communicate through Whatsapp using two different numbers. These rotten vile grossly deceitful crooked stealing low life scum bags need locking up asap never to be released!.
2019-12-27 03:08:53
183.81.50.203 attack
Dec 26 15:51:21 icecube postfix/smtpd[82723]: NOQUEUE: reject: RCPT from unknown[183.81.50.203]: 554 5.7.1 Service unavailable; Client host [183.81.50.203] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/183.81.50.203; from= to= proto=ESMTP helo=
2019-12-27 02:58:52
83.56.44.36 attackspam
Lines containing failures of 83.56.44.36
Dec 24 06:44:42 nextcloud sshd[30651]: Invalid user sheilah from 83.56.44.36 port 60722
Dec 24 06:44:42 nextcloud sshd[30651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.56.44.36
Dec 24 06:44:45 nextcloud sshd[30651]: Failed password for invalid user sheilah from 83.56.44.36 port 60722 ssh2
Dec 24 06:44:45 nextcloud sshd[30651]: Received disconnect from 83.56.44.36 port 60722:11: Bye Bye [preauth]
Dec 24 06:44:45 nextcloud sshd[30651]: Disconnected from invalid user sheilah 83.56.44.36 port 60722 [preauth]
Dec 24 07:00:06 nextcloud sshd[2730]: Invalid user dl from 83.56.44.36 port 54282
Dec 24 07:00:06 nextcloud sshd[2730]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.56.44.36
Dec 24 07:00:08 nextcloud sshd[2730]: Failed password for invalid user dl from 83.56.44.36 port 54282 ssh2
Dec 24 07:00:08 nextcloud sshd[2730]: Received disconnect........
------------------------------
2019-12-27 02:36:56
49.88.112.114 attack
Dec 26 08:41:19 php1 sshd\[29266\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
Dec 26 08:41:21 php1 sshd\[29266\]: Failed password for root from 49.88.112.114 port 41321 ssh2
Dec 26 08:42:34 php1 sshd\[29343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
Dec 26 08:42:36 php1 sshd\[29343\]: Failed password for root from 49.88.112.114 port 53246 ssh2
Dec 26 08:46:32 php1 sshd\[29646\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
2019-12-27 02:54:03
72.18.217.226 attack
$f2bV_matches
2019-12-27 02:47:03
112.29.140.224 attack
$f2bV_matches
2019-12-27 02:36:21

Recently Reported IPs

2606:4700:10::ac43:2264 164.52.105.76 170.82.91.3 20.208.130.25
2606:4700:10::6814:9991 2606:4700:10::6814:6309 2606:4700:10::6814:6316 2606:4700:10::6814:7934
2606:4700:10::ac43:2204 2606:4700:10::6816:422d 2606:4700:10::6816:4433 2606:4700:10::6814:4424
2606:4700:10::6814:4679 45.88.192.117 182.138.158.54 175.30.48.192
123.145.13.125 121.56.214.174 114.97.190.44 103.137.160.189