城市(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: 52.192.0.0 - 52.223.191.255
CIDR: 52.220.0.0/15, 52.208.0.0/13, 52.223.0.0/17, 52.192.0.0/12, 52.222.0.0/16, 52.216.0.0/14, 52.223.128.0/18
NetName: AT-88-Z
NetHandle: NET-52-192-0-0-1
Parent: NET52 (NET-52-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 2015-09-02
Updated: 2020-09-24
Ref: https://rdap.arin.net/registry/ip/52.192.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: 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
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
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
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 <<>> 52.201.219.92
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56134
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;52.201.219.92. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026012801 1800 900 604800 86400
;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 29 05:00:28 CST 2026
;; MSG SIZE rcvd: 10692.219.201.52.in-addr.arpa domain name pointer ec2-52-201-219-92.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
92.219.201.52.in-addr.arpa name = ec2-52-201-219-92.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 23.231.110.131 | attackbotsspam | (From eric@talkwithcustomer.com) Hi, My name is Eric and I was looking at a few different sites online and came across your site shannonchiropractic.com. I must say - your website is very impressive. I am seeing your website on the first page of the Search Engine. Have you noticed that 70 percent of visitors who leave your website will never return? In most cases, this means that 95 percent to 98 percent of your marketing efforts are going to waste, not to mention that you are losing more money in customer acquisition costs than you need to. As a business person, the time and money you put into your marketing efforts is extremely valuable. So why let it go to waste? Our users have seen staggering improvements in conversions with insane growths of 150 percent going upwards of 785 percent. Are you ready to unlock the highest conversion revenue from each of your website visitors? TalkWithCustomer is a widget which captures a website visitor’s Name, Email address and Phone Number and then c |
2020-02-19 01:51:07 |
| 103.110.18.116 | attackspambots | MultiHost/MultiPort Probe, Scan, Hack - |
2020-02-19 01:58:42 |
| 59.126.123.192 | attackbotsspam | Feb 18 13:22:07 system,error,critical: login failure for user admin from 59.126.123.192 via telnet Feb 18 13:22:14 system,error,critical: login failure for user root from 59.126.123.192 via telnet Feb 18 13:22:16 system,error,critical: login failure for user Administrator from 59.126.123.192 via telnet Feb 18 13:22:21 system,error,critical: login failure for user admin from 59.126.123.192 via telnet Feb 18 13:22:27 system,error,critical: login failure for user guest from 59.126.123.192 via telnet Feb 18 13:22:29 system,error,critical: login failure for user root from 59.126.123.192 via telnet Feb 18 13:22:35 system,error,critical: login failure for user admin from 59.126.123.192 via telnet Feb 18 13:22:44 system,error,critical: login failure for user root from 59.126.123.192 via telnet Feb 18 13:22:46 system,error,critical: login failure for user root from 59.126.123.192 via telnet Feb 18 13:22:48 system,error,critical: login failure for user admin from 59.126.123.192 via telnet |
2020-02-19 01:59:37 |
| 49.88.112.65 | attack | Feb 18 07:34:32 hanapaa sshd\[31669\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.65 user=root Feb 18 07:34:34 hanapaa sshd\[31669\]: Failed password for root from 49.88.112.65 port 47754 ssh2 Feb 18 07:35:42 hanapaa sshd\[31751\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.65 user=root Feb 18 07:35:44 hanapaa sshd\[31751\]: Failed password for root from 49.88.112.65 port 33733 ssh2 Feb 18 07:35:46 hanapaa sshd\[31751\]: Failed password for root from 49.88.112.65 port 33733 ssh2 |
2020-02-19 01:41:46 |
| 103.110.18.23 | attackspambots | Automatic report - Port Scan Attack |
2020-02-19 01:45:50 |
| 192.42.116.13 | attackbots | Invalid user test from 192.42.116.13 port 38698 |
2020-02-19 01:26:00 |
| 103.110.18.86 | attackspam | Automatic report - Port Scan Attack |
2020-02-19 01:25:07 |
| 180.250.125.53 | attackbots | 2020-02-18T15:05:56.261418scmdmz1 sshd[15111]: Invalid user bwadmin from 180.250.125.53 port 56546 2020-02-18T15:05:56.264277scmdmz1 sshd[15111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.125.53 2020-02-18T15:05:56.261418scmdmz1 sshd[15111]: Invalid user bwadmin from 180.250.125.53 port 56546 2020-02-18T15:05:58.485459scmdmz1 sshd[15111]: Failed password for invalid user bwadmin from 180.250.125.53 port 56546 ssh2 2020-02-18T15:09:12.744789scmdmz1 sshd[15406]: Invalid user test from 180.250.125.53 port 48758 ... |
2020-02-19 01:34:43 |
| 185.209.0.32 | attackbots | firewall-block, port(s): 18500/tcp |
2020-02-19 01:32:32 |
| 186.138.196.50 | attackspambots | $f2bV_matches |
2020-02-19 01:38:01 |
| 5.196.226.217 | attackbotsspam | Feb 18 18:39:43 legacy sshd[26799]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.226.217 Feb 18 18:39:46 legacy sshd[26799]: Failed password for invalid user asi from 5.196.226.217 port 34072 ssh2 Feb 18 18:44:43 legacy sshd[26986]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.226.217 ... |
2020-02-19 01:54:47 |
| 103.110.18.87 | attackspambots | MultiHost/MultiPort Probe, Scan, Hack - |
2020-02-19 01:24:24 |
| 107.167.180.11 | attackbots | Automatic report - Banned IP Access |
2020-02-19 01:54:04 |
| 159.89.181.213 | attack | Feb 18 12:20:06 hgb10502 sshd[4562]: Did not receive identification string from 159.89.181.213 port 49928 Feb 18 12:20:40 hgb10502 sshd[4628]: User r.r from 159.89.181.213 not allowed because not listed in AllowUsers Feb 18 12:20:40 hgb10502 sshd[4628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.181.213 user=r.r Feb 18 12:20:43 hgb10502 sshd[4628]: Failed password for invalid user r.r from 159.89.181.213 port 47170 ssh2 Feb 18 12:20:43 hgb10502 sshd[4628]: Received disconnect from 159.89.181.213 port 47170:11: Normal Shutdown, Thank you for playing [preauth] Feb 18 12:20:43 hgb10502 sshd[4628]: Disconnected from 159.89.181.213 port 47170 [preauth] Feb 18 12:21:23 hgb10502 sshd[4691]: Invalid user oracle from 159.89.181.213 port 58344 Feb 18 12:21:25 hgb10502 sshd[4691]: Failed password for invalid user oracle from 159.89.181.213 port 58344 ssh2 Feb 18 12:21:25 hgb10502 sshd[4691]: Received disconnect from 159.89.181.2........ ------------------------------- |
2020-02-19 01:30:57 |
| 13.67.91.234 | attackbots | Feb 18 13:46:24 web8 sshd\[20289\]: Invalid user rahul1 from 13.67.91.234 Feb 18 13:46:24 web8 sshd\[20289\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.67.91.234 Feb 18 13:46:26 web8 sshd\[20289\]: Failed password for invalid user rahul1 from 13.67.91.234 port 53808 ssh2 Feb 18 13:49:46 web8 sshd\[21910\]: Invalid user chuck from 13.67.91.234 Feb 18 13:49:46 web8 sshd\[21910\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.67.91.234 |
2020-02-19 01:57:52 |