Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Sydney

Region: New South Wales

Country: Australia

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
#
# 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.64.0.0/12, 52.0.0.0/10
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:        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


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

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

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 info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.62.80.192
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17267
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;52.62.80.192.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026020201 1800 900 604800 86400

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 03 03:30:11 CST 2026
;; MSG SIZE  rcvd: 105
Host info
192.80.62.52.in-addr.arpa domain name pointer ec2-52-62-80-192.ap-southeast-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
192.80.62.52.in-addr.arpa	name = ec2-52-62-80-192.ap-southeast-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
14.116.222.207 attackbots
RDP Bruteforce
2020-02-26 10:36:32
222.186.52.139 attackspambots
2020-02-25T12:21:26.146680vps773228.ovh.net sshd[19628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.52.139  user=root
2020-02-25T12:21:27.893916vps773228.ovh.net sshd[19628]: Failed password for root from 222.186.52.139 port 27294 ssh2
2020-02-25T12:21:30.152180vps773228.ovh.net sshd[19628]: Failed password for root from 222.186.52.139 port 27294 ssh2
2020-02-25T12:21:32.685965vps773228.ovh.net sshd[19628]: Failed password for root from 222.186.52.139 port 27294 ssh2
2020-02-26T03:30:01.302606vps773228.ovh.net sshd[23486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.52.139  user=root
2020-02-26T03:30:03.344190vps773228.ovh.net sshd[23486]: Failed password for root from 222.186.52.139 port 44976 ssh2
2020-02-26T03:30:01.302606vps773228.ovh.net sshd[23486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.52.139  user=root
2020-02-26T03:3
...
2020-02-26 11:10:11
149.202.4.243 attack
Feb 25 18:35:47 askasleikir sshd[88807]: Failed password for invalid user jomar from 149.202.4.243 port 45492 ssh2
2020-02-26 10:54:03
35.193.123.76 attack
Feb 26 02:40:02 server sshd[1613510]: Failed password for invalid user upload from 35.193.123.76 port 37038 ssh2
Feb 26 02:47:43 server sshd[1615055]: Failed password for invalid user informix from 35.193.123.76 port 54578 ssh2
Feb 26 02:55:04 server sshd[1616592]: Failed password for invalid user qtss from 35.193.123.76 port 43880 ssh2
2020-02-26 10:53:12
219.92.249.52 attackbots
SSH Brute-Forcing (server2)
2020-02-26 10:59:53
142.93.232.102 attack
(sshd) Failed SSH login from 142.93.232.102 (NL/Netherlands/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 26 03:24:22 amsweb01 sshd[6443]: Invalid user lty from 142.93.232.102 port 52354
Feb 26 03:24:24 amsweb01 sshd[6443]: Failed password for invalid user lty from 142.93.232.102 port 52354 ssh2
Feb 26 03:26:21 amsweb01 sshd[6593]: Invalid user fredportela from 142.93.232.102 port 55420
Feb 26 03:26:23 amsweb01 sshd[6593]: Failed password for invalid user fredportela from 142.93.232.102 port 55420 ssh2
Feb 26 03:27:48 amsweb01 sshd[6695]: Invalid user git_user from 142.93.232.102 port 53888
2020-02-26 10:44:23
45.55.214.64 attack
Feb 26 02:33:54 srv01 sshd[32258]: Invalid user cpanelrrdtool from 45.55.214.64 port 49218
Feb 26 02:33:54 srv01 sshd[32258]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.214.64
Feb 26 02:33:54 srv01 sshd[32258]: Invalid user cpanelrrdtool from 45.55.214.64 port 49218
Feb 26 02:33:56 srv01 sshd[32258]: Failed password for invalid user cpanelrrdtool from 45.55.214.64 port 49218 ssh2
Feb 26 02:40:27 srv01 sshd[4429]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.214.64  user=root
Feb 26 02:40:29 srv01 sshd[4429]: Failed password for root from 45.55.214.64 port 46004 ssh2
...
2020-02-26 11:13:33
187.59.65.80 attackbots
Automatic report - Port Scan Attack
2020-02-26 10:53:43
106.12.76.49 attack
Feb 26 01:59:18 mail sshd[18190]: Invalid user fctr from 106.12.76.49
...
2020-02-26 10:54:25
74.82.47.24 attack
Honeypot hit.
2020-02-26 10:44:54
106.54.114.248 attack
Feb 26 01:15:52 ns382633 sshd\[28030\]: Invalid user yhk from 106.54.114.248 port 34588
Feb 26 01:15:52 ns382633 sshd\[28030\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.114.248
Feb 26 01:15:53 ns382633 sshd\[28030\]: Failed password for invalid user yhk from 106.54.114.248 port 34588 ssh2
Feb 26 01:44:43 ns382633 sshd\[32712\]: Invalid user pellegrini from 106.54.114.248 port 53918
Feb 26 01:44:43 ns382633 sshd\[32712\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.114.248
2020-02-26 11:09:35
121.35.103.28 attackspam
Unauthorized connection attempt from IP address 121.35.103.28 on Port 445(SMB)
2020-02-26 10:35:27
200.69.81.10 attackbots
Sending SPAM email
2020-02-26 10:43:05
69.229.6.42 attackbotsspam
Feb 26 03:21:32 server sshd\[16561\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.229.6.42  user=root
Feb 26 03:21:34 server sshd\[16561\]: Failed password for root from 69.229.6.42 port 47572 ssh2
Feb 26 03:45:07 server sshd\[21769\]: Invalid user fabian from 69.229.6.42
Feb 26 03:45:07 server sshd\[21769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.229.6.42 
Feb 26 03:45:09 server sshd\[21769\]: Failed password for invalid user fabian from 69.229.6.42 port 48412 ssh2
...
2020-02-26 10:42:21
171.244.166.18 attackbots
Feb 26 02:19:59 lvps87-230-18-106 sshd[22257]: Address 171.244.166.18 maps to dynamic-ip-adsl.viettel.vn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Feb 26 02:19:59 lvps87-230-18-106 sshd[22257]: Invalid user ubuntu from 171.244.166.18
Feb 26 02:19:59 lvps87-230-18-106 sshd[22257]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.244.166.18 
Feb 26 02:20:01 lvps87-230-18-106 sshd[22257]: Failed password for invalid user ubuntu from 171.244.166.18 port 44514 ssh2
Feb 26 02:20:01 lvps87-230-18-106 sshd[22257]: Received disconnect from 171.244.166.18: 11: Bye Bye [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=171.244.166.18
2020-02-26 11:04:08

Recently Reported IPs

178.239.123.228 111.178.61.25 49.234.76.21 209.54.104.45
47.92.146.183 157.173.102.59 149.1.126.65 149.1.126.197
116.1.215.173 34.82.98.72 42.180.227.130 95.164.5.48
54.85.134.46 43.136.167.214 103.236.95.173 144.172.108.12
222.254.34.14 194.187.177.99 194.187.177.201 3.91.58.30