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:
IP Type Details Datetime
52.42.253.100 attack
11/26/2019-11:29:07.732906 52.42.253.100 Protocol: 6 SURICATA TLS invalid record/traffic
2019-11-26 18:47:12
52.42.253.100 attackspambots
11/25/2019-10:02:02.227775 52.42.253.100 Protocol: 6 SURICATA TLS invalid record/traffic
2019-11-25 18:12:29
52.42.253.100 attack
11/25/2019-06:20:02.050391 52.42.253.100 Protocol: 6 SURICATA TLS invalid record/traffic
2019-11-25 13:20:50
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.42.253.241
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18891
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;52.42.253.241.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 15:48:37 CST 2025
;; MSG SIZE  rcvd: 106
Host info
241.253.42.52.in-addr.arpa domain name pointer ec2-52-42-253-241.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
241.253.42.52.in-addr.arpa	name = ec2-52-42-253-241.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.176.27.246 attack
05/20/2020-17:26:52.032465 185.176.27.246 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-05-21 05:28:20
165.22.31.24 attack
REQUESTED PAGE: /wp-login.php
2020-05-21 05:46:21
194.61.26.34 attackbots
May 20 17:59:15 server sshd[3530]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.61.26.34
May 20 17:59:17 server sshd[3530]: Failed password for invalid user Admin from 194.61.26.34 port 40357 ssh2
May 20 17:59:18 server sshd[3532]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.61.26.34
...
2020-05-21 05:38:57
165.227.135.34 attack
May 20 21:17:42 melroy-server sshd[14634]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.135.34 
May 20 21:17:44 melroy-server sshd[14634]: Failed password for invalid user eug from 165.227.135.34 port 45272 ssh2
...
2020-05-21 05:43:10
206.132.109.108 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-05-21 05:56:40
152.250.252.179 attack
Too many connections or unauthorized access detected from Arctic banned ip
2020-05-21 05:57:11
47.30.208.185 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-05-21 05:49:16
179.189.113.114 attackspam
SMB Server BruteForce Attack
2020-05-21 05:32:38
36.110.27.122 attackspambots
Invalid user ka from 36.110.27.122 port 58546
2020-05-21 05:26:57
134.209.102.196 attack
Automatic report BANNED IP
2020-05-21 05:22:36
178.207.60.161 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-05-21 05:43:42
180.142.131.43 attack
Honeypot attack, port: 81, PTR: PTR record not found
2020-05-21 05:55:35
92.46.23.14 attack
SSH login attempts with user(s): noc.
2020-05-21 05:50:18
104.140.188.10 attackspam
port scan and connect, tcp 23 (telnet)
2020-05-21 05:24:55
89.176.9.98 attack
DATE:2020-05-20 21:08:40, IP:89.176.9.98, PORT:ssh SSH brute force auth (docker-dc)
2020-05-21 05:36:49

Recently Reported IPs

145.17.118.31 209.148.92.137 90.113.137.227 231.248.65.206
30.136.235.41 134.102.231.0 245.223.195.135 16.210.252.79
241.31.29.149 30.192.56.165 30.50.228.63 140.91.69.124
205.239.216.0 161.5.52.148 132.62.242.27 213.1.143.219
236.240.106.129 200.181.182.18 9.212.201.136 248.46.0.173