City: San Jose
Region: California
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.
#
# start
NetRange: 18.32.0.0 - 18.255.255.255
CIDR: 18.128.0.0/9, 18.32.0.0/11, 18.64.0.0/10
NetName: AT-88-Z
NetHandle: NET-18-32-0-0-1
Parent: NET18 (NET-18-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 2019-10-07
Updated: 2021-02-10
Ref: https://rdap.arin.net/registry/ip/18.32.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
# end
# start
NetRange: 18.145.0.0 - 18.145.255.255
CIDR: 18.145.0.0/16
NetName: AMAZON-SFO
NetHandle: NET-18-145-0-0-2
Parent: AT-88-Z (NET-18-32-0-0-1)
NetType: Reallocated
OriginAS:
Organization: Amazon.com, Inc. (AMAZO-48)
RegDate: 2017-09-14
Updated: 2021-02-10
Ref: https://rdap.arin.net/registry/ip/18.145.0.0
OrgName: Amazon.com, Inc.
OrgId: AMAZO-48
Address: 1200 12th Ave South
City: Seattle
StateProv: WA
PostalCode: 98144
Country: US
RegDate: 2011-08-11
Updated: 2026-11-12
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/entity/AMAZO-48
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
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
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
# 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 <<>> 18.145.194.152
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28875
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;18.145.194.152. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026112100 1800 900 604800 86400
;; Query time: 85 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Nov 22 02:00:02 CST 2026
;; MSG SIZE rcvd: 107
152.194.145.18.in-addr.arpa domain name pointer ec2-18-145-194-152.us-west-1.compute.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
152.194.145.18.in-addr.arpa name = ec2-18-145-194-152.us-west-1.compute.amazonaws.com.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 120.138.9.104 | attack | Jul 11 22:11:47 xeon sshd[30145]: Failed password for invalid user user from 120.138.9.104 port 16936 ssh2 |
2019-07-12 04:23:38 |
| 85.209.0.11 | attackspam | Port scan on 21 port(s): 12350 13254 18780 20398 27359 29509 34298 36258 36717 40169 40326 41377 42436 43005 44090 45624 47012 49172 57648 58435 58518 |
2019-07-12 04:45:58 |
| 51.104.7.122 | attackbotsspam | Apr 25 16:55:48 mail sshd\[53031\]: Invalid user hl from 51.104.7.122 Apr 25 16:55:48 mail sshd\[53031\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.104.7.122 Apr 25 16:55:50 mail sshd\[53031\]: Failed password for invalid user hl from 51.104.7.122 port 45348 ssh2 Apr 25 16:59:45 mail sshd\[53063\]: Invalid user jr from 51.104.7.122 Apr 25 16:59:45 mail sshd\[53063\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.104.7.122 Apr 25 16:59:47 mail sshd\[53063\]: Failed password for invalid user jr from 51.104.7.122 port 55006 ssh2 Apr 25 17:02:23 mail sshd\[53088\]: Invalid user odoo from 51.104.7.122 Apr 25 17:02:23 mail sshd\[53088\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.104.7.122 Apr 25 17:02:25 mail sshd\[53088\]: Failed password for invalid user odoo from 51.104.7.122 port 53202 ssh2 Apr 25 17:05:19 mail sshd\[53144\]: Invalid user uo from 51.104.7.122 |
2019-07-12 04:44:50 |
| 95.107.0.61 | attackspambots | 19/7/11@10:09:16: FAIL: Alarm-Intrusion address from=95.107.0.61 ... |
2019-07-12 04:49:59 |
| 145.239.10.217 | attackspam | Jun 28 03:23:30 server sshd\[179307\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.10.217 user=gnats Jun 28 03:23:32 server sshd\[179307\]: Failed password for gnats from 145.239.10.217 port 40272 ssh2 Jun 28 03:26:29 server sshd\[180082\]: Invalid user test2 from 145.239.10.217 ... |
2019-07-12 04:12:33 |
| 104.152.52.23 | attackspam | A portscan was detected. Details about the event:
Time.............: 2019-07-11 09:46:07
Source IP address: 104.152.52.23 (internettl.org)
--
System Uptime : 42 days 0 hours 16 minutes
System Load : 0.24
System Version : Sophos UTM 9.603-1 |
2019-07-12 04:20:57 |
| 125.115.180.39 | attackbots | Jul 11 19:35:56 fr01 sshd[9512]: Invalid user service from 125.115.180.39 Jul 11 19:35:56 fr01 sshd[9512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.115.180.39 Jul 11 19:35:56 fr01 sshd[9512]: Invalid user service from 125.115.180.39 Jul 11 19:35:58 fr01 sshd[9512]: Failed password for invalid user service from 125.115.180.39 port 8982 ssh2 Jul 11 19:35:56 fr01 sshd[9512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.115.180.39 Jul 11 19:35:56 fr01 sshd[9512]: Invalid user service from 125.115.180.39 Jul 11 19:35:58 fr01 sshd[9512]: Failed password for invalid user service from 125.115.180.39 port 8982 ssh2 Jul 11 19:36:01 fr01 sshd[9512]: Failed password for invalid user service from 125.115.180.39 port 8982 ssh2 ... |
2019-07-12 04:52:02 |
| 142.93.245.174 | attackspam | May 6 12:59:51 server sshd\[153739\]: Invalid user test from 142.93.245.174 May 6 12:59:51 server sshd\[153739\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.245.174 May 6 12:59:53 server sshd\[153739\]: Failed password for invalid user test from 142.93.245.174 port 36206 ssh2 ... |
2019-07-12 04:47:22 |
| 125.64.94.221 | attack | Scanning (more than 2 packets) random ports - tries to find possible vulnerable services |
2019-07-12 04:24:54 |
| 173.254.213.10 | attackspam | WordPress wp-login brute force :: 173.254.213.10 0.044 BYPASS [12/Jul/2019:04:52:52 1000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 4630 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2019-07-12 04:30:38 |
| 144.217.237.117 | attack | Apr 23 07:36:44 server sshd\[62896\]: Invalid user mythtv from 144.217.237.117 Apr 23 07:36:44 server sshd\[62896\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.237.117 Apr 23 07:36:46 server sshd\[62896\]: Failed password for invalid user mythtv from 144.217.237.117 port 58932 ssh2 ... |
2019-07-12 04:24:09 |
| 198.98.53.237 | attackspam | NAME : PONYNET-06 CIDR : 198.98.48.0/20 SYN Flood DDoS Attack USA - Wyoming - block certain countries :) IP: 198.98.53.237 Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN - data recovery https://help-dysk.pl |
2019-07-12 04:41:34 |
| 144.21.80.96 | attackbotsspam | Jun 4 12:03:23 server sshd\[132375\]: Invalid user school from 144.21.80.96 Jun 4 12:03:23 server sshd\[132375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.21.80.96 Jun 4 12:03:25 server sshd\[132375\]: Failed password for invalid user school from 144.21.80.96 port 37097 ssh2 ... |
2019-07-12 04:24:33 |
| 145.239.120.171 | attackbotsspam | Apr 18 13:43:08 server sshd\[151400\]: Invalid user jboss from 145.239.120.171 Apr 18 13:43:08 server sshd\[151400\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.120.171 Apr 18 13:43:10 server sshd\[151400\]: Failed password for invalid user jboss from 145.239.120.171 port 58028 ssh2 ... |
2019-07-12 04:11:45 |
| 142.93.58.123 | attackbotsspam | Jul 6 11:51:20 server sshd\[2190\]: Invalid user frontdesk from 142.93.58.123 Jul 6 11:51:20 server sshd\[2190\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.58.123 Jul 6 11:51:22 server sshd\[2190\]: Failed password for invalid user frontdesk from 142.93.58.123 port 33636 ssh2 ... |
2019-07-12 04:38:27 |