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-2025, American Registry for Internet Numbers, Ltd.
#
# start
NetRange: 44.192.0.0 - 44.255.255.255
CIDR: 44.192.0.0/10
NetName: AMAZO-4
NetHandle: NET-44-192-0-0-1
Parent: NET44 (NET-44-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon.com, Inc. (AMAZO-4)
RegDate: 2019-07-18
Updated: 2019-07-18
Ref: https://rdap.arin.net/registry/ip/44.192.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: 2022-09-30
Comment: For details of this service please see
Comment: http://ec2.amazonaws.com
Ref: https://rdap.arin.net/registry/entity/AMAZO-4
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
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
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
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
# end
# start
NetRange: 44.224.0.0 - 44.255.255.255
CIDR: 44.224.0.0/11
NetName: AMAZO-ZPDX
NetHandle: NET-44-224-0-0-1
Parent: AMAZO-4 (NET-44-192-0-0-1)
NetType: Reallocated
OriginAS:
Organization: Amazon.com, Inc. (AMAZO-47)
RegDate: 2019-08-01
Updated: 2019-08-01
Ref: https://rdap.arin.net/registry/ip/44.224.0.0
OrgName: Amazon.com, Inc.
OrgId: AMAZO-47
Address: EC2, EC2 1200 12th Ave South
City: Seattle
StateProv: WA
PostalCode: 98144
Country: US
RegDate: 2011-05-10
Updated: 2021-07-22
Ref: https://rdap.arin.net/registry/entity/AMAZO-47
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
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
# 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-2025, American Registry for Internet Numbers, Ltd.
#
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 44.248.99.51
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46727
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;44.248.99.51. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025113001 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 01 10:30:54 CST 2025
;; MSG SIZE rcvd: 105
51.99.248.44.in-addr.arpa domain name pointer ec2-44-248-99-51.us-west-2.compute.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
51.99.248.44.in-addr.arpa name = ec2-44-248-99-51.us-west-2.compute.amazonaws.com.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 61.163.2.246 | attackspam | Brute force attack to crack SMTP password (port 25 / 587) |
2019-07-04 01:59:43 |
| 46.101.242.117 | attack | Jul 3 18:40:54 Proxmox sshd\[27267\]: Invalid user cms from 46.101.242.117 port 45974 Jul 3 18:40:54 Proxmox sshd\[27267\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.242.117 Jul 3 18:40:57 Proxmox sshd\[27267\]: Failed password for invalid user cms from 46.101.242.117 port 45974 ssh2 Jul 3 18:43:36 Proxmox sshd\[29476\]: Invalid user zw from 46.101.242.117 port 49862 Jul 3 18:43:36 Proxmox sshd\[29476\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.242.117 Jul 3 18:43:37 Proxmox sshd\[29476\]: Failed password for invalid user zw from 46.101.242.117 port 49862 ssh2 |
2019-07-04 01:46:31 |
| 185.232.67.13 | attackbots | 03.07.2019 16:02:58 Connection to port 1723 blocked by firewall |
2019-07-04 01:20:17 |
| 178.138.97.98 | attackspam | 2019-07-03 14:23:30 H=([178.138.97.98]) [178.138.97.98]:47205 I=[10.100.18.25]:25 F= |
2019-07-04 01:24:29 |
| 106.51.80.18 | attack | Jul 3 08:04:59 ingram sshd[21511]: Did not receive identification string from 106.51.80.18 Jul 3 08:05:04 ingram sshd[21519]: Invalid user admin from 106.51.80.18 Jul 3 08:05:04 ingram sshd[21519]: Failed none for invalid user admin from 106.51.80.18 port 65216 ssh2 Jul 3 08:05:05 ingram sshd[21519]: Failed password for invalid user admin from 106.51.80.18 port 65216 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=106.51.80.18 |
2019-07-04 01:19:15 |
| 178.46.161.110 | attackspam | failed_logins |
2019-07-04 01:18:02 |
| 154.125.43.157 | attack | Jul 3 15:14:56 econome sshd[7993]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.125.43.157 user=r.r Jul 3 15:14:57 econome sshd[7993]: Failed password for r.r from 154.125.43.157 port 33436 ssh2 Jul 3 15:15:00 econome sshd[7993]: Failed password for r.r from 154.125.43.157 port 33436 ssh2 Jul 3 15:15:02 econome sshd[7993]: Failed password for r.r from 154.125.43.157 port 33436 ssh2 Jul 3 15:15:04 econome sshd[7993]: Failed password for r.r from 154.125.43.157 port 33436 ssh2 Jul 3 15:15:06 econome sshd[7993]: Failed password for r.r from 154.125.43.157 port 33436 ssh2 Jul 3 15:15:08 econome sshd[7993]: Failed password for r.r from 154.125.43.157 port 33436 ssh2 Jul 3 15:15:08 econome sshd[7993]: Disconnecting: Too many authentication failures for r.r from 154.125.43.157 port 33436 ssh2 [preauth] Jul 3 15:15:08 econome sshd[7993]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.12........ ------------------------------- |
2019-07-04 01:37:06 |
| 119.28.16.71 | attackspam | firewall-block, port(s): 445/tcp |
2019-07-04 02:00:52 |
| 119.29.89.200 | attackspam | Jul 3 13:48:30 localhost sshd\[7375\]: Invalid user guang from 119.29.89.200 port 55486 Jul 3 13:48:30 localhost sshd\[7375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.89.200 Jul 3 13:48:32 localhost sshd\[7375\]: Failed password for invalid user guang from 119.29.89.200 port 55486 ssh2 ... |
2019-07-04 01:50:38 |
| 79.135.81.45 | attackbotsspam | Sending SPAM email |
2019-07-04 01:58:33 |
| 50.73.137.241 | attackbotsspam | Automatic report - Web App Attack |
2019-07-04 01:45:16 |
| 52.73.169.169 | attackbotsspam | Honeypot attack, application: ssdp, PTR: scanner2.scanning.cybergreen.net. |
2019-07-04 01:49:56 |
| 220.197.219.214 | attackbots | Port 1433 Scan |
2019-07-04 01:38:17 |
| 200.209.174.38 | attackspam | Jul 3 15:20:41 fr01 sshd[27489]: Invalid user jboss from 200.209.174.38 Jul 3 15:20:41 fr01 sshd[27489]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.209.174.38 Jul 3 15:20:41 fr01 sshd[27489]: Invalid user jboss from 200.209.174.38 Jul 3 15:20:43 fr01 sshd[27489]: Failed password for invalid user jboss from 200.209.174.38 port 32850 ssh2 ... |
2019-07-04 01:47:16 |
| 187.104.200.188 | attackspam | Jul 3 14:35:23 vtv3 sshd\[11990\]: Invalid user edu from 187.104.200.188 port 40044 Jul 3 14:35:23 vtv3 sshd\[11990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.104.200.188 Jul 3 14:35:25 vtv3 sshd\[11990\]: Failed password for invalid user edu from 187.104.200.188 port 40044 ssh2 Jul 3 14:43:56 vtv3 sshd\[16543\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.104.200.188 user=sys Jul 3 14:43:57 vtv3 sshd\[16543\]: Failed password for sys from 187.104.200.188 port 57132 ssh2 Jul 3 15:00:21 vtv3 sshd\[24448\]: Invalid user amanda from 187.104.200.188 port 34848 Jul 3 15:00:21 vtv3 sshd\[24448\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.104.200.188 Jul 3 15:00:23 vtv3 sshd\[24448\]: Failed password for invalid user amanda from 187.104.200.188 port 34848 ssh2 Jul 3 15:08:45 vtv3 sshd\[28743\]: Invalid user muriel from 187.104.200.188 port 52014 Jul |
2019-07-04 01:25:01 |