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

;; QUESTION SECTION:
;3.104.53.7.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 27 12:21:11 CST 2025
;; MSG SIZE  rcvd: 103
Host info
7.53.104.3.in-addr.arpa domain name pointer ec2-3-104-53-7.ap-southeast-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
7.53.104.3.in-addr.arpa	name = ec2-3-104-53-7.ap-southeast-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
52.130.85.214 attack
Jul 22 16:00:20 server1 sshd\[16872\]: Invalid user syam from 52.130.85.214
Jul 22 16:00:20 server1 sshd\[16872\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.130.85.214 
Jul 22 16:00:23 server1 sshd\[16872\]: Failed password for invalid user syam from 52.130.85.214 port 51880 ssh2
Jul 22 16:05:07 server1 sshd\[18207\]: Invalid user uts from 52.130.85.214
Jul 22 16:05:07 server1 sshd\[18207\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.130.85.214 
...
2020-07-23 06:18:44
45.134.179.243 attackbotsspam
 TCP (SYN) 45.134.179.243:56842 -> port 3389, len 44
2020-07-23 06:13:24
188.11.237.35 attackspam
Unauthorized connection attempt detected from IP address 188.11.237.35 to port 445
2020-07-23 06:30:30
2.184.168.180 attack
Unauthorized connection attempt detected from IP address 2.184.168.180 to port 23
2020-07-23 06:45:52
79.23.160.248 attackbotsspam
Unauthorized connection attempt detected from IP address 79.23.160.248 to port 81
2020-07-23 06:41:01
66.70.142.231 attackbots
Invalid user testing from 66.70.142.231 port 46402
2020-07-23 06:14:30
177.55.142.75 attack
Unauthorized connection attempt detected from IP address 177.55.142.75 to port 81
2020-07-23 06:32:18
125.26.193.176 attackbots
Automatic report - Port Scan Attack
2020-07-23 06:17:55
139.59.7.251 attackspambots
Invalid user why from 139.59.7.251 port 25508
2020-07-23 06:26:23
93.174.93.139 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 84 - port: 81 proto: tcp cat: Misc Attackbytes: 60
2020-07-23 06:37:32
85.100.63.179 attack
Unauthorized connection attempt detected from IP address 85.100.63.179 to port 23
2020-07-23 06:39:44
150.109.229.30 attackbotsspam
Unauthorized connection attempt detected from IP address 150.109.229.30 to port 8007
2020-07-23 06:34:35
191.254.129.163 attackspam
Unauthorized connection attempt detected from IP address 191.254.129.163 to port 8080
2020-07-23 06:48:11
66.249.75.95 attackbots
Automatic report - Banned IP Access
2020-07-23 06:18:31
154.68.196.6 attackspam
Port probing on unauthorized port 23
2020-07-23 06:34:10

Recently Reported IPs

116.217.221.100 50.125.228.6 52.19.214.50 122.123.63.183
147.72.23.173 107.136.232.165 154.150.76.139 21.217.149.252
44.162.162.66 147.115.92.248 185.252.22.158 33.220.50.229
17.115.172.200 192.184.246.207 192.6.110.87 9.121.105.47
207.220.149.238 76.143.139.7 70.111.151.106 84.2.113.193