City: Ashburn
Region: Virginia
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: 3.0.0.0 - 3.127.255.255
CIDR: 3.0.0.0/9
NetName: AT-88-Z
NetHandle: NET-3-0-0-0-1
Parent: NET3 (NET-3-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 2017-12-20
Updated: 2022-05-18
Ref: https://rdap.arin.net/registry/ip/3.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
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
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
OrgDNSHandle: DNS1131-ARIN
OrgDNSName: DNS
OrgDNSPhone: +1-202-555-0000
OrgDNSEmail: ipmanagement+dns@amazon.com
OrgDNSRef: https://rdap.arin.net/registry/entity/DNS1131-ARIN
# end
# start
NetRange: 3.80.0.0 - 3.95.255.255
CIDR: 3.80.0.0/12
NetName: AMAZON-IAD
NetHandle: NET-3-80-0-0-1
Parent: AT-88-Z (NET-3-0-0-0-1)
NetType: Reallocated
OriginAS:
Organization: Amazon Data Services Northern Virginia (ADSN-1)
RegDate: 2018-08-22
Updated: 2018-08-22
Ref: https://rdap.arin.net/registry/ip/3.80.0.0
OrgName: Amazon Data Services Northern Virginia
OrgId: ADSN-1
Address: 13200 Woodland Park Road
City: Herndon
StateProv: VA
PostalCode: 20171
Country: US
RegDate: 2018-04-25
Updated: 2025-08-14
Ref: https://rdap.arin.net/registry/entity/ADSN-1
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
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
# 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 <<>> 3.85.201.48
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7248
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;3.85.201.48. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026080101 1800 900 604800 86400
;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Aug 02 08:30:34 CST 2026
;; MSG SIZE rcvd: 10448.201.85.3.in-addr.arpa domain name pointer ec2-3-85-201-48.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
48.201.85.3.in-addr.arpa name = ec2-3-85-201-48.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 75.98.144.15 | attack | Brute-force attempt banned |
2019-12-19 05:20:44 |
| 84.22.40.25 | attackspam | Unauthorized connection attempt from IP address 84.22.40.25 on Port 445(SMB) |
2019-12-19 05:29:08 |
| 79.110.192.122 | attackbots | Dec 18 20:04:42 work-partkepr sshd\[18060\]: Invalid user mall from 79.110.192.122 port 34694 Dec 18 20:04:42 work-partkepr sshd\[18060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.110.192.122 ... |
2019-12-19 05:22:03 |
| 54.39.145.59 | attackbotsspam | Dec 18 22:33:56 [host] sshd[22746]: Invalid user host from 54.39.145.59 Dec 18 22:33:56 [host] sshd[22746]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.145.59 Dec 18 22:33:59 [host] sshd[22746]: Failed password for invalid user host from 54.39.145.59 port 47788 ssh2 |
2019-12-19 05:46:34 |
| 139.59.213.125 | attackspambots | Dec 18 18:25:44 reporting6 sshd[23557]: Did not receive identification string from 139.59.213.125 Dec 18 18:28:04 reporting6 sshd[24755]: reveeclipse mapping checking getaddrinfo for 353897.cloudwaysapps.com [139.59.213.125] failed - POSSIBLE BREAK-IN ATTEMPT! Dec 18 18:28:04 reporting6 sshd[24755]: User r.r from 139.59.213.125 not allowed because not listed in AllowUsers Dec 18 18:28:04 reporting6 sshd[24755]: Failed password for invalid user r.r from 139.59.213.125 port 37836 ssh2 Dec 18 18:28:10 reporting6 sshd[24814]: reveeclipse mapping checking getaddrinfo for 353897.cloudwaysapps.com [139.59.213.125] failed - POSSIBLE BREAK-IN ATTEMPT! Dec 18 18:28:10 reporting6 sshd[24814]: User r.r from 139.59.213.125 not allowed because not listed in AllowUsers Dec 18 18:28:10 reporting6 sshd[24814]: Failed password for invalid user r.r from 139.59.213.125 port 42598 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=139.59.213.125 |
2019-12-19 05:36:47 |
| 150.107.213.95 | attackbotsspam | Dec 16 21:15:50 linuxrulz sshd[18705]: Invalid user herington from 150.107.213.95 port 55803 Dec 16 21:15:50 linuxrulz sshd[18705]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.107.213.95 Dec 16 21:15:52 linuxrulz sshd[18705]: Failed password for invalid user herington from 150.107.213.95 port 55803 ssh2 Dec 16 21:15:52 linuxrulz sshd[18705]: Received disconnect from 150.107.213.95 port 55803:11: Bye Bye [preauth] Dec 16 21:15:52 linuxrulz sshd[18705]: Disconnected from 150.107.213.95 port 55803 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=150.107.213.95 |
2019-12-19 05:36:14 |
| 103.113.64.6 | attackbots | Unauthorized connection attempt detected from IP address 103.113.64.6 to port 445 |
2019-12-19 05:27:10 |
| 218.78.46.81 | attack | --- report --- Dec 18 16:07:23 sshd: Connection from 218.78.46.81 port 52604 Dec 18 16:07:24 sshd: Invalid user operator from 218.78.46.81 Dec 18 16:07:26 sshd: Failed password for invalid user operator from 218.78.46.81 port 52604 ssh2 Dec 18 16:07:26 sshd: Received disconnect from 218.78.46.81: 11: Bye Bye [preauth] |
2019-12-19 05:52:20 |
| 70.65.174.69 | attack | Dec 18 22:17:03 ArkNodeAT sshd\[26744\]: Invalid user michael from 70.65.174.69 Dec 18 22:17:03 ArkNodeAT sshd\[26744\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.65.174.69 Dec 18 22:17:05 ArkNodeAT sshd\[26744\]: Failed password for invalid user michael from 70.65.174.69 port 36410 ssh2 |
2019-12-19 05:30:08 |
| 151.237.170.56 | attackbotsspam | Unauthorised access (Dec 18) SRC=151.237.170.56 LEN=48 PREC=0x20 TTL=113 ID=3603 DF TCP DPT=445 WINDOW=8192 SYN |
2019-12-19 05:50:48 |
| 213.162.215.184 | attackbotsspam | port scan and connect, tcp 80 (http) |
2019-12-19 05:33:46 |
| 94.67.107.8 | attackbots | Unauthorized connection attempt from IP address 94.67.107.8 on Port 445(SMB) |
2019-12-19 05:46:10 |
| 109.173.40.60 | attackbots | Dec 18 19:38:39 sip sshd[2420]: Failed password for www-data from 109.173.40.60 port 49402 ssh2 Dec 18 19:52:13 sip sshd[2587]: Failed password for backup from 109.173.40.60 port 52554 ssh2 |
2019-12-19 05:43:05 |
| 40.92.42.36 | attack | Dec 18 17:30:45 debian-2gb-vpn-nbg1-1 kernel: [1057809.443441] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=40.92.42.36 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=230 ID=12771 DF PROTO=TCP SPT=60128 DPT=25 WINDOW=0 RES=0x00 ACK RST URGP=0 |
2019-12-19 05:53:49 |
| 116.72.16.15 | attackspam | Dec 18 10:46:14 Ubuntu-1404-trusty-64-minimal sshd\[18741\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.72.16.15 user=root Dec 18 10:46:16 Ubuntu-1404-trusty-64-minimal sshd\[18741\]: Failed password for root from 116.72.16.15 port 44816 ssh2 Dec 18 22:13:32 Ubuntu-1404-trusty-64-minimal sshd\[18019\]: Invalid user user4 from 116.72.16.15 Dec 18 22:13:32 Ubuntu-1404-trusty-64-minimal sshd\[18019\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.72.16.15 Dec 18 22:13:33 Ubuntu-1404-trusty-64-minimal sshd\[18019\]: Failed password for invalid user user4 from 116.72.16.15 port 46668 ssh2 |
2019-12-19 05:24:26 |