城市(city): San Jose
省份(region): California
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
#
# 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: 2026-04-17
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
OrgDNSHandle: DNS1131-ARIN
OrgDNSName: DNS
OrgDNSPhone: +1-202-555-0000
OrgDNSEmail: ipmanagement+dns@amazon.com
OrgDNSRef: https://rdap.arin.net/registry/entity/DNS1131-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
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
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
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
# 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
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
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
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
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
# 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 9.10.3-P4-Ubuntu <<>> 3.101.72.75
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64319
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;3.101.72.75. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026102000 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 21 01:30:04 CST 2026
;; MSG SIZE rcvd: 10475.72.101.3.in-addr.arpa domain name pointer ec2-3-101-72-75.us-west-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
75.72.101.3.in-addr.arpa name = ec2-3-101-72-75.us-west-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 180.242.134.253 | attack | 34567/tcp [2019-09-23]1pkt |
2019-09-24 09:17:10 |
| 106.13.93.161 | attackspambots | Sep 24 03:16:04 markkoudstaal sshd[3129]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.93.161 Sep 24 03:16:05 markkoudstaal sshd[3129]: Failed password for invalid user han from 106.13.93.161 port 43262 ssh2 Sep 24 03:20:37 markkoudstaal sshd[3566]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.93.161 |
2019-09-24 09:32:30 |
| 36.75.174.39 | attackbots | Automatic report - Port Scan Attack |
2019-09-24 09:16:46 |
| 189.59.205.236 | attackspambots | 445/tcp [2019-09-23]1pkt |
2019-09-24 09:12:32 |
| 201.16.251.121 | attackspambots | Sep 23 14:40:51 aiointranet sshd\[14312\]: Invalid user ke from 201.16.251.121 Sep 23 14:40:51 aiointranet sshd\[14312\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.16.251.121 Sep 23 14:40:53 aiointranet sshd\[14312\]: Failed password for invalid user ke from 201.16.251.121 port 24011 ssh2 Sep 23 14:46:03 aiointranet sshd\[14775\]: Invalid user hdfs from 201.16.251.121 Sep 23 14:46:03 aiointranet sshd\[14775\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.16.251.121 |
2019-09-24 08:53:58 |
| 128.199.178.188 | attack | detected by Fail2Ban |
2019-09-24 09:36:22 |
| 177.101.161.32 | attackspam | 23/tcp [2019-09-23]1pkt |
2019-09-24 08:56:32 |
| 167.249.42.173 | attackbots | 445/tcp [2019-09-23]1pkt |
2019-09-24 09:21:35 |
| 150.109.63.147 | attackbots | Sep 24 03:16:38 vps sshd[7459]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.109.63.147 Sep 24 03:16:39 vps sshd[7459]: Failed password for invalid user inaldo from 150.109.63.147 port 46330 ssh2 Sep 24 03:31:59 vps sshd[7754]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.109.63.147 ... |
2019-09-24 09:34:13 |
| 175.139.242.49 | attack | 2019-09-23T20:54:51.8032741495-001 sshd\[33912\]: Invalid user 1qaz2wsx from 175.139.242.49 port 48214 2019-09-23T20:54:51.8062701495-001 sshd\[33912\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.139.242.49 2019-09-23T20:54:53.6078231495-001 sshd\[33912\]: Failed password for invalid user 1qaz2wsx from 175.139.242.49 port 48214 ssh2 2019-09-23T20:59:18.7412811495-001 sshd\[34277\]: Invalid user qwerasdfzxcv from 175.139.242.49 port 6341 2019-09-23T20:59:18.7485801495-001 sshd\[34277\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.139.242.49 2019-09-23T20:59:20.8715961495-001 sshd\[34277\]: Failed password for invalid user qwerasdfzxcv from 175.139.242.49 port 6341 ssh2 ... |
2019-09-24 09:14:51 |
| 67.213.75.130 | attackspam | Sep 24 02:47:25 dedicated sshd[25699]: Invalid user osram from 67.213.75.130 port 49896 |
2019-09-24 09:03:15 |
| 181.198.211.62 | attack | Honeypot attack, port: 23, PTR: host-181-198-211-62.netlife.ec. |
2019-09-24 09:19:20 |
| 220.247.174.14 | attack | Automatic report - Banned IP Access |
2019-09-24 09:20:40 |
| 164.132.56.243 | attackspambots | Sep 24 03:43:13 taivassalofi sshd[96776]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.56.243 Sep 24 03:43:16 taivassalofi sshd[96776]: Failed password for invalid user wendel from 164.132.56.243 port 51449 ssh2 ... |
2019-09-24 09:01:16 |
| 171.236.91.38 | attackspambots | Honeypot attack, port: 23, PTR: dynamic-adsl.viettel.vn. |
2019-09-24 09:35:34 |