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: unknown

Region: unknown

Country: United States of America (the)

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

;; QUESTION SECTION:
;52.53.124.157.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 23 04:00:25 CST 2025
;; MSG SIZE  rcvd: 106
Host info
157.124.53.52.in-addr.arpa domain name pointer ec2-52-53-124-157.us-west-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
157.124.53.52.in-addr.arpa	name = ec2-52-53-124-157.us-west-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
124.156.109.210 attack
Feb 19 01:04:07 dedicated sshd[27939]: Invalid user pi from 124.156.109.210 port 43602
2020-02-19 08:12:29
103.80.36.34 attackbotsspam
Feb 18 22:00:15 work-partkepr sshd\[13243\]: User mysql from 103.80.36.34 not allowed because not listed in AllowUsers
Feb 18 22:00:15 work-partkepr sshd\[13243\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.80.36.34  user=mysql
...
2020-02-19 08:34:04
190.151.105.182 attackspam
Invalid user test2 from 190.151.105.182 port 43740
2020-02-19 08:04:49
104.194.8.7 attackspambots
104.194.8.7 was recorded 6 times by 6 hosts attempting to connect to the following ports: 5070. Incident counter (4h, 24h, all-time): 6, 6, 6
2020-02-19 08:25:25
83.174.197.243 attack
Unauthorized connection attempt from IP address 83.174.197.243 on Port 445(SMB)
2020-02-19 08:02:10
66.249.76.126 attackbotsspam
MYH,DEF GET /adminer-4.6.2.php
2020-02-19 08:21:49
112.205.235.3 attackspambots
Unauthorized connection attempt from IP address 112.205.235.3 on Port 445(SMB)
2020-02-19 07:59:59
190.186.107.178 attackbotsspam
Unauthorized connection attempt from IP address 190.186.107.178 on Port 445(SMB)
2020-02-19 08:00:22
177.126.141.11 attackspam
trying to access non-authorized port
2020-02-19 08:07:59
145.255.72.41 attackbotsspam
Unauthorized connection attempt from IP address 145.255.72.41 on Port 445(SMB)
2020-02-19 08:12:14
106.124.142.64 attackbots
Invalid user testtest from 106.124.142.64 port 44136
2020-02-19 08:33:36
192.241.221.89 attack
Unauthorized connection attempt detected from IP address 192.241.221.89 to port 1433
2020-02-19 07:58:46
182.72.154.30 attack
Feb 18 13:50:02 sachi sshd\[4944\]: Invalid user tom from 182.72.154.30
Feb 18 13:50:02 sachi sshd\[4944\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.154.30
Feb 18 13:50:04 sachi sshd\[4944\]: Failed password for invalid user tom from 182.72.154.30 port 50587 ssh2
Feb 18 13:52:46 sachi sshd\[5152\]: Invalid user amandabackup from 182.72.154.30
Feb 18 13:52:46 sachi sshd\[5152\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.154.30
2020-02-19 07:59:08
88.204.170.230 attack
Email rejected due to spam filtering
2020-02-19 08:25:46
54.36.182.244 attack
Invalid user sa from 54.36.182.244 port 47897
2020-02-19 08:29:49

Recently Reported IPs

95.234.99.215 76.25.255.19 18.104.115.181 151.107.177.81
139.17.34.246 71.77.193.81 215.33.38.68 51.172.39.161
241.232.147.82 97.126.248.145 73.228.107.66 8.92.168.103
131.220.130.172 190.111.49.146 179.42.110.220 13.86.153.44
94.235.75.217 71.122.115.76 236.29.113.79 145.105.60.85