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.38.252.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3240
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;52.38.252.242.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 25 06:45:25 CST 2024
;; MSG SIZE  rcvd: 106
Host info
242.252.38.52.in-addr.arpa domain name pointer ec2-52-38-252-242.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
242.252.38.52.in-addr.arpa	name = ec2-52-38-252-242.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
138.197.133.232 attack
Brute force SMTP login attempted.
...
2019-08-10 03:44:37
67.225.139.208 attackbotsspam
WordPress wp-login brute force :: 67.225.139.208 0.068 BYPASS [10/Aug/2019:03:33:38  1000] [censored_4] "POST /wp-login.php HTTP/1.1" 200 3989 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-08-10 04:21:06
95.253.111.145 attackspam
Aug  9 21:30:11 OPSO sshd\[16707\]: Invalid user shoutcast from 95.253.111.145 port 38268
Aug  9 21:30:11 OPSO sshd\[16707\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.253.111.145
Aug  9 21:30:13 OPSO sshd\[16707\]: Failed password for invalid user shoutcast from 95.253.111.145 port 38268 ssh2
Aug  9 21:34:03 OPSO sshd\[17224\]: Invalid user zabbix from 95.253.111.145 port 43346
Aug  9 21:34:03 OPSO sshd\[17224\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.253.111.145
2019-08-10 03:45:40
110.249.212.46 attack
116x Blocked Connections on two of our networks and 7 different IPs focusing on 27 specific ports - (Focused Probe began 29Jul on multiple of our networks and is documented daily. Ports of interest are: 80, 81, 443, 803, 3128, 3328, 5555, 8000, 8080, 8081, 8085, 8090, 8118, 8123, 8888, 8989, 9000, 9090, 9191, 9797, 9999, 10102, 11223, 18186, 34599, 37564, & 55555)
2019-08-10 04:05:37
194.61.26.30 attackbotsspam
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-08-10 03:50:39
193.188.22.188 attackspambots
2019-08-09T19:27:33.720008abusebot-5.cloudsearch.cf sshd\[18469\]: Invalid user mother from 193.188.22.188 port 41552
2019-08-10 03:47:43
51.254.99.208 attackspam
Aug  9 20:33:47 srv-4 sshd\[27511\]: Invalid user sabine from 51.254.99.208
Aug  9 20:33:47 srv-4 sshd\[27511\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.99.208
Aug  9 20:33:49 srv-4 sshd\[27511\]: Failed password for invalid user sabine from 51.254.99.208 port 60642 ssh2
...
2019-08-10 04:11:21
2405:201:806:6fe1:6da2:fc21:f66d:d2eb attack
PHI,WP GET /wp-login.php
2019-08-10 03:39:26
138.121.62.63 attackspam
Brute force SMTP login attempted.
...
2019-08-10 04:09:33
103.52.52.22 attack
Aug  9 21:29:25 OPSO sshd\[16433\]: Invalid user temp from 103.52.52.22 port 59529
Aug  9 21:29:25 OPSO sshd\[16433\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.52.52.22
Aug  9 21:29:27 OPSO sshd\[16433\]: Failed password for invalid user temp from 103.52.52.22 port 59529 ssh2
Aug  9 21:33:43 OPSO sshd\[17140\]: Invalid user library from 103.52.52.22 port 52954
Aug  9 21:33:43 OPSO sshd\[17140\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.52.52.22
2019-08-10 03:41:11
165.22.187.244 attack
08/09/2019-14:54:22.512629 165.22.187.244 Protocol: 6 ET COMPROMISED Known Compromised or Hostile Host Traffic group 7
2019-08-10 03:56:13
180.250.85.227 attack
Aug  9 14:04:13 aat-srv002 sshd[17490]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.85.227
Aug  9 14:04:15 aat-srv002 sshd[17490]: Failed password for invalid user test from 180.250.85.227 port 40186 ssh2
Aug  9 14:09:53 aat-srv002 sshd[17590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.85.227
Aug  9 14:09:55 aat-srv002 sshd[17590]: Failed password for invalid user foc from 180.250.85.227 port 37632 ssh2
...
2019-08-10 03:42:04
138.0.7.212 attackbotsspam
Brute force SMTP login attempted.
...
2019-08-10 04:14:05
203.229.201.231 attackbotsspam
SSH authentication failure x 6 reported by Fail2Ban
...
2019-08-10 03:53:36
77.247.181.163 attackspambots
Aug  9 21:17:04 mail sshd\[6227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.247.181.163  user=root
Aug  9 21:17:06 mail sshd\[6227\]: Failed password for root from 77.247.181.163 port 1502 ssh2
Aug  9 21:17:09 mail sshd\[6227\]: Failed password for root from 77.247.181.163 port 1502 ssh2
Aug  9 21:17:14 mail sshd\[6227\]: Failed password for root from 77.247.181.163 port 1502 ssh2
Aug  9 21:17:17 mail sshd\[6227\]: Failed password for root from 77.247.181.163 port 1502 ssh2
2019-08-10 03:51:02

Recently Reported IPs

19.226.91.116 200.14.186.91 17.55.129.220 173.102.10.196
192.49.80.252 253.72.18.68 30.50.238.210 73.39.19.82
212.183.233.102 108.136.116.185 151.58.141.107 41.202.158.191
109.183.201.58 162.60.35.122 125.100.69.8 222.147.105.188
112.115.202.158 208.4.229.104 33.249.61.170 72.147.115.12