城市(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.
#
NetRange: 107.20.0.0 - 107.23.255.255
CIDR: 107.20.0.0/14
NetName: AMAZON-EC2-8
NetHandle: NET-107-20-0-0-1
Parent: NET107 (NET-107-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon.com, Inc. (AMAZO-4)
RegDate: 2011-05-03
Updated: 2014-09-03
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/ip/107.20.0.0
OrgName: Amazon.com, Inc.
OrgId: AMAZO-4
Address: Amazon Web Services, Inc.
Address: P.O. Box 81226
City: Seattle
StateProv: WA
PostalCode: 98108-1226
Country: US
RegDate: 2005-09-29
Updated: 2026-04-17
Comment: For details of this service please see
Comment: http://ec2.amazonaws.com
Ref: https://rdap.arin.net/registry/entity/AMAZO-4
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
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
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: 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
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
#
# 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 <<>> 107.21.0.67
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11450
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;107.21.0.67. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026100801 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 09 07:33:33 CST 2026
;; MSG SIZE rcvd: 104
67.0.21.107.in-addr.arpa domain name pointer ec2-107-21-0-67.compute-1.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
67.0.21.107.in-addr.arpa name = ec2-107-21-0-67.compute-1.amazonaws.com.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 58.32.210.244 | attackspambots | Aug 28 18:54:16 root sshd[16545]: Invalid user deployer from 58.32.210.244 ... |
2020-08-29 01:28:06 |
| 187.170.226.136 | attack | Aug 28 07:36:46 nxxxxxxx0 sshd[6302]: reveeclipse mapping checking getaddrinfo for dsl-187-170-226-136-dyn.prod-infinhostnameum.com.mx [187.170.226.136] failed - POSSIBLE BREAK-IN ATTEMPT! Aug 28 07:36:46 nxxxxxxx0 sshd[6302]: Invalid user serveri from 187.170.226.136 Aug 28 07:36:46 nxxxxxxx0 sshd[6302]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.170.226.136 Aug 28 07:36:49 nxxxxxxx0 sshd[6302]: Failed password for invalid user serveri from 187.170.226.136 port 50822 ssh2 Aug 28 07:36:49 nxxxxxxx0 sshd[6302]: Received disconnect from 187.170.226.136: 11: Bye Bye [preauth] Aug 28 07:46:22 nxxxxxxx0 sshd[6907]: reveeclipse mapping checking getaddrinfo for dsl-187-170-226-136-dyn.prod-infinhostnameum.com.mx [187.170.226.136] failed - POSSIBLE BREAK-IN ATTEMPT! Aug 28 07:46:22 nxxxxxxx0 sshd[6907]: Invalid user user from 187.170.226.136 Aug 28 07:46:22 nxxxxxxx0 sshd[6907]: pam_unix(sshd:auth): authentication failure; logna........ ------------------------------- |
2020-08-29 01:25:54 |
| 81.178.234.84 | attackspam | Invalid user sinus from 81.178.234.84 port 57776 |
2020-08-29 01:51:35 |
| 114.149.239.217 | attack | Lines containing failures of 114.149.239.217 Aug 28 15:24:12 MAKserver05 sshd[31385]: Invalid user pi from 114.149.239.217 port 58266 Aug 28 15:24:12 MAKserver05 sshd[31387]: Invalid user pi from 114.149.239.217 port 58278 Aug 28 15:24:12 MAKserver05 sshd[31385]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.149.239.217 Aug 28 15:24:12 MAKserver05 sshd[31387]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.149.239.217 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=114.149.239.217 |
2020-08-29 01:39:50 |
| 201.116.194.210 | attack | Aug 28 17:31:37 124388 sshd[20441]: Invalid user gian from 201.116.194.210 port 4223 Aug 28 17:31:37 124388 sshd[20441]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.116.194.210 Aug 28 17:31:37 124388 sshd[20441]: Invalid user gian from 201.116.194.210 port 4223 Aug 28 17:31:39 124388 sshd[20441]: Failed password for invalid user gian from 201.116.194.210 port 4223 ssh2 Aug 28 17:33:55 124388 sshd[20536]: Invalid user lek from 201.116.194.210 port 42127 |
2020-08-29 01:44:11 |
| 180.76.161.203 | attackspam | Aug 28 16:10:08 sigma sshd\[419\]: Invalid user zwg from 180.76.161.203Aug 28 16:10:09 sigma sshd\[419\]: Failed password for invalid user zwg from 180.76.161.203 port 41298 ssh2 ... |
2020-08-29 01:17:48 |
| 118.96.237.26 | attackbotsspam | Telnetd brute force attack detected by fail2ban |
2020-08-29 01:39:22 |
| 2604:a880:800:a1::325:1 | attackbotsspam | 2604:a880:800:a1::325:1 - - [28/Aug/2020:06:04:58 -0600] "GET /wp-login.php HTTP/1.1" 301 476 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-08-29 01:21:38 |
| 204.195.21.57 | attack | IP 204.195.21.57 attacked honeypot on port: 23 at 8/28/2020 7:21:22 AM |
2020-08-29 01:31:37 |
| 104.243.25.75 | attackbotsspam | Time: Fri Aug 28 17:03:35 2020 +0000 IP: 104.243.25.75 (US/United States/104.243.25.75.16clouds.com) Failures: 5 (sshd) Interval: 3600 seconds Blocked: Permanent Block [LF_SSHD] Log entries: Aug 28 16:45:48 pv-14-ams2 sshd[8932]: Invalid user admin from 104.243.25.75 port 45476 Aug 28 16:45:50 pv-14-ams2 sshd[8932]: Failed password for invalid user admin from 104.243.25.75 port 45476 ssh2 Aug 28 16:57:07 pv-14-ams2 sshd[14392]: Invalid user jonas from 104.243.25.75 port 48870 Aug 28 16:57:09 pv-14-ams2 sshd[14392]: Failed password for invalid user jonas from 104.243.25.75 port 48870 ssh2 Aug 28 17:03:31 pv-14-ams2 sshd[3329]: Invalid user mapred from 104.243.25.75 port 44684 |
2020-08-29 01:26:42 |
| 218.92.0.158 | attack | Aug 28 13:31:09 NPSTNNYC01T sshd[8397]: Failed password for root from 218.92.0.158 port 25446 ssh2 Aug 28 13:31:13 NPSTNNYC01T sshd[8397]: Failed password for root from 218.92.0.158 port 25446 ssh2 Aug 28 13:31:16 NPSTNNYC01T sshd[8397]: Failed password for root from 218.92.0.158 port 25446 ssh2 Aug 28 13:31:19 NPSTNNYC01T sshd[8397]: Failed password for root from 218.92.0.158 port 25446 ssh2 ... |
2020-08-29 01:35:17 |
| 162.62.26.192 | attackspam | IP 162.62.26.192 attacked honeypot on port: 35 at 8/28/2020 5:04:11 AM |
2020-08-29 01:55:51 |
| 175.143.29.91 | attackbotsspam | Attempts against non-existent wp-login |
2020-08-29 01:17:09 |
| 106.12.33.78 | attackspambots | Aug 28 15:07:46 rocket sshd[22468]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.33.78 Aug 28 15:07:48 rocket sshd[22468]: Failed password for invalid user info from 106.12.33.78 port 47548 ssh2 ... |
2020-08-29 01:55:02 |
| 149.202.41.25 | attackbotsspam | Invalid user trx from 149.202.41.25 port 58812 |
2020-08-29 01:38:54 |