城市(city): Ashburn
省份(region): Virginia
国家(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: 13.200.0.0 - 13.239.255.255
CIDR: 13.224.0.0/12, 13.200.0.0/13, 13.208.0.0/12
NetName: AT-88-Z
NetHandle: NET-13-200-0-0-1
Parent: NET13 (NET-13-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 2019-10-01
Updated: 2021-02-10
Ref: https://rdap.arin.net/registry/ip/13.200.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: 13.216.0.0 - 13.223.255.255
CIDR: 13.216.0.0/13
NetName: AMAZON-IAD
NetHandle: NET-13-216-0-0-1
Parent: AT-88-Z (NET-13-200-0-0-1)
NetType: Reallocated
OriginAS:
Organization: Amazon Data Services Northern Virginia (ADSN-1)
RegDate: 2024-09-27
Updated: 2024-09-27
Ref: https://rdap.arin.net/registry/ip/13.216.0.0
OrgName: Amazon Data Services Northern Virginia
OrgId: ADSN-1
Address: 13200 Woodland Park Road
City: Herndon
StateProv: VA
PostalCode: 20171
Country: US
RegDate: 2018-04-25
Updated: 2025-08-14
Ref: https://rdap.arin.net/registry/entity/ADSN-1
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
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
#
# 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 <<>> 13.220.107.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59257
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;13.220.107.9. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026102402 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 25 08:30:59 CST 2026
;; MSG SIZE rcvd: 1059.107.220.13.in-addr.arpa domain name pointer ec2-13-220-107-9.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
9.107.220.13.in-addr.arpa name = ec2-13-220-107-9.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 141.98.9.156 | attackspambots | $f2bV_matches | Triggered by Fail2Ban at Vostok web server |
2020-05-02 01:21:28 |
| 215.49.47.34 | attackbotsspam | May 01 07:45:17 tcp 0 0 r.ca:22 215.49.47.34:20802 SYN_RECV |
2020-05-02 01:42:23 |
| 200.73.129.85 | attackbots | 2020-04-30 19:54:00 server sshd[22615]: Failed password for invalid user mysqluser from 200.73.129.85 port 48858 ssh2 |
2020-05-02 01:11:39 |
| 125.99.159.87 | attack | May 1 16:58:04 game-panel sshd[9514]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.99.159.87 May 1 16:58:06 game-panel sshd[9514]: Failed password for invalid user nell from 125.99.159.87 port 57138 ssh2 May 1 16:58:31 game-panel sshd[9516]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.99.159.87 |
2020-05-02 01:12:31 |
| 182.61.57.103 | attackspam | May 1 16:08:21 roki-contabo sshd\[16418\]: Invalid user vanessa from 182.61.57.103 May 1 16:08:21 roki-contabo sshd\[16418\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.57.103 May 1 16:08:24 roki-contabo sshd\[16418\]: Failed password for invalid user vanessa from 182.61.57.103 port 53518 ssh2 May 1 16:15:59 roki-contabo sshd\[16529\]: Invalid user user1 from 182.61.57.103 May 1 16:15:59 roki-contabo sshd\[16529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.57.103 ... |
2020-05-02 01:22:23 |
| 162.243.137.205 | attack | MultiHost/MultiPort Probe, Scan, Hack - |
2020-05-02 01:48:41 |
| 106.13.84.192 | attack | May 1 17:25:36 vlre-nyc-1 sshd\[8647\]: Invalid user docker from 106.13.84.192 May 1 17:25:36 vlre-nyc-1 sshd\[8647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.84.192 May 1 17:25:38 vlre-nyc-1 sshd\[8647\]: Failed password for invalid user docker from 106.13.84.192 port 39588 ssh2 May 1 17:30:09 vlre-nyc-1 sshd\[8803\]: Invalid user fzm from 106.13.84.192 May 1 17:30:09 vlre-nyc-1 sshd\[8803\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.84.192 ... |
2020-05-02 01:40:22 |
| 202.21.127.189 | attack | May 1 18:18:58 sigma sshd\[6785\]: Invalid user hts from 202.21.127.189May 1 18:19:01 sigma sshd\[6785\]: Failed password for invalid user hts from 202.21.127.189 port 56248 ssh2 ... |
2020-05-02 01:30:16 |
| 180.76.141.184 | attack | $f2bV_matches |
2020-05-02 01:17:57 |
| 1.20.149.146 | attackbots | Telnet/23 MH Probe, Scan, BF, Hack - |
2020-05-02 01:28:49 |
| 49.135.34.206 | attackspambots | May 1 02:01:50 our-server-hostname sshd[1369]: Invalid user user from 49.135.34.206 May 1 02:01:50 our-server-hostname sshd[1369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=w0109-49-135-34-206.uqwimax.jp May 1 02:01:52 our-server-hostname sshd[1369]: Failed password for invalid user user from 49.135.34.206 port 40210 ssh2 May 1 02:17:05 our-server-hostname sshd[4001]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=w0109-49-135-34-206.uqwimax.jp user=r.r May 1 02:17:07 our-server-hostname sshd[4001]: Failed password for r.r from 49.135.34.206 port 33424 ssh2 May 1 02:32:34 our-server-hostname sshd[6519]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=w0109-49-135-34-206.uqwimax.jp user=r.r May 1 02:32:35 our-server-hostname sshd[6519]: Failed password for r.r from 49.135.34.206 port 54874 ssh2 May 1 02:42:19 our-server-hostname sshd[8........ ------------------------------- |
2020-05-02 01:34:43 |
| 220.123.194.50 | attack | 2375/tcp 2375/tcp 2375/tcp [2020-04-27/30]3pkt |
2020-05-02 01:29:15 |
| 128.199.138.31 | attack | (sshd) Failed SSH login from 128.199.138.31 (SG/Singapore/staging.fiuzu.com): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May 1 17:24:00 elude sshd[27873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.138.31 user=root May 1 17:24:01 elude sshd[27873]: Failed password for root from 128.199.138.31 port 41871 ssh2 May 1 17:37:17 elude sshd[29988]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.138.31 user=root May 1 17:37:19 elude sshd[29988]: Failed password for root from 128.199.138.31 port 39387 ssh2 May 1 17:41:48 elude sshd[30804]: Invalid user financeiro from 128.199.138.31 port 43853 |
2020-05-02 01:06:17 |
| 122.51.62.212 | attackbots | SSH authentication failure x 6 reported by Fail2Ban ... |
2020-05-02 01:20:11 |
| 37.134.29.228 | attackbots | May 01 07:40:17 tcp 0 0 r.ca:22 37.134.29.228:13585 SYN_RECV |
2020-05-02 01:25:14 |