City: Boardman
Region: Oregon
Country: United States
Internet Service Provider: 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.0.0.0 - 52.79.255.255
CIDR: 52.0.0.0/10, 52.64.0.0/12
NetName: AT-88-Z
NetHandle: NET-52-0-0-0-1
Parent: NET52 (NET-52-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 1991-12-19
Updated: 2024-02-05
Comment: Geofeed http://ip-ranges.amazonaws.com/geo-ip-feed.csv
Ref: https://rdap.arin.net/registry/ip/52.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
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
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
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.35.192.183
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33395
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;52.35.192.183. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026112001 1800 900 604800 86400
;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Nov 21 04:29:37 CST 2026
;; MSG SIZE rcvd: 106
183.192.35.52.in-addr.arpa domain name pointer ec2-52-35-192-183.us-west-2.compute.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
183.192.35.52.in-addr.arpa name = ec2-52-35-192-183.us-west-2.compute.amazonaws.com.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 118.160.126.199 | attack | 23/tcp [2019-08-24]1pkt |
2019-08-25 04:38:33 |
| 1.255.101.72 | attack | Aug 24 11:18:47 TCP Attack: SRC=1.255.101.72 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=57 DF PROTO=TCP SPT=50901 DPT=80 WINDOW=29200 RES=0x00 SYN URGP=0 |
2019-08-25 04:58:21 |
| 212.129.148.117 | attack | Invalid user error from 212.129.148.117 port 54972 |
2019-08-25 05:07:20 |
| 188.166.31.205 | attackbots | Aug 24 08:31:38 plusreed sshd[24536]: Invalid user admin from 188.166.31.205 ... |
2019-08-25 04:32:57 |
| 45.115.99.38 | attackspam | 2019-08-24T22:31:32.265271 sshd[5769]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.115.99.38 user=root 2019-08-24T22:31:34.351407 sshd[5769]: Failed password for root from 45.115.99.38 port 46216 ssh2 2019-08-24T22:36:18.567155 sshd[5816]: Invalid user awsbilling from 45.115.99.38 port 40306 2019-08-24T22:36:18.581695 sshd[5816]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.115.99.38 2019-08-24T22:36:18.567155 sshd[5816]: Invalid user awsbilling from 45.115.99.38 port 40306 2019-08-24T22:36:20.597505 sshd[5816]: Failed password for invalid user awsbilling from 45.115.99.38 port 40306 ssh2 ... |
2019-08-25 04:58:48 |
| 177.184.70.8 | attackbots | $f2bV_matches |
2019-08-25 04:40:02 |
| 13.56.181.243 | attack | [portscan] Port scan |
2019-08-25 05:10:59 |
| 103.221.228.70 | attack | firewall-block, port(s): 445/tcp |
2019-08-25 04:41:33 |
| 106.12.103.98 | attack | Aug 24 08:49:24 lcprod sshd\[7229\]: Invalid user jeff from 106.12.103.98 Aug 24 08:49:24 lcprod sshd\[7229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.103.98 Aug 24 08:49:26 lcprod sshd\[7229\]: Failed password for invalid user jeff from 106.12.103.98 port 49606 ssh2 Aug 24 08:54:42 lcprod sshd\[7752\]: Invalid user theresa from 106.12.103.98 Aug 24 08:54:42 lcprod sshd\[7752\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.103.98 |
2019-08-25 04:52:04 |
| 103.243.252.244 | attackbotsspam | invalid user |
2019-08-25 05:00:31 |
| 139.170.149.161 | attackspambots | Aug 24 15:47:24 localhost sshd\[19725\]: Invalid user Jewel from 139.170.149.161 port 44796 Aug 24 15:47:24 localhost sshd\[19725\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.170.149.161 Aug 24 15:47:26 localhost sshd\[19725\]: Failed password for invalid user Jewel from 139.170.149.161 port 44796 ssh2 |
2019-08-25 04:50:07 |
| 119.10.115.36 | attackbots | Aug 24 17:01:00 v22018053744266470 sshd[12460]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.10.115.36 Aug 24 17:01:02 v22018053744266470 sshd[12460]: Failed password for invalid user hauptinhaltsverzeichnis from 119.10.115.36 port 36128 ssh2 Aug 24 17:03:41 v22018053744266470 sshd[12630]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.10.115.36 ... |
2019-08-25 04:50:27 |
| 43.226.38.229 | attackspam | Aug 24 01:48:46 kapalua sshd\[24907\]: Invalid user buster from 43.226.38.229 Aug 24 01:48:46 kapalua sshd\[24907\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.38.229 Aug 24 01:48:47 kapalua sshd\[24907\]: Failed password for invalid user buster from 43.226.38.229 port 45514 ssh2 Aug 24 01:52:49 kapalua sshd\[25279\]: Invalid user proffice from 43.226.38.229 Aug 24 01:52:49 kapalua sshd\[25279\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.38.229 |
2019-08-25 05:06:04 |
| 210.209.72.243 | attack | Aug 24 22:53:20 root sshd[950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.209.72.243 Aug 24 22:53:22 root sshd[950]: Failed password for invalid user argo from 210.209.72.243 port 57568 ssh2 Aug 24 22:58:29 root sshd[1029]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.209.72.243 ... |
2019-08-25 05:06:29 |
| 196.202.6.124 | attack | 19/8/24@07:19:43: FAIL: Alarm-Intrusion address from=196.202.6.124 ... |
2019-08-25 04:56:52 |