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

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

;; QUESTION SECTION:
;53.204.128.94.			IN	A

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

;; Query time: 45 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 16:41:09 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 94.128.204.53.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 94.128.204.53.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
107.172.143.244 attackbots
Feb  7 15:24:34 meumeu sshd[2347]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.172.143.244 
Feb  7 15:24:36 meumeu sshd[2347]: Failed password for invalid user yfd from 107.172.143.244 port 36787 ssh2
Feb  7 15:32:46 meumeu sshd[3709]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.172.143.244 
...
2020-02-07 22:52:14
185.209.0.32 attack
trying to access non-authorized port
2020-02-07 22:49:21
183.82.120.139 attackbotsspam
Feb  5 02:53:07 HOST sshd[18583]: Failed password for invalid user bernd from 183.82.120.139 port 50548 ssh2
Feb  5 02:53:07 HOST sshd[18583]: Received disconnect from 183.82.120.139: 11: Bye Bye [preauth]
Feb  5 03:14:42 HOST sshd[19542]: reveeclipse mapping checking getaddrinfo for broadband.actcorp.in [183.82.120.139] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  5 03:14:43 HOST sshd[19542]: Failed password for invalid user kuan from 183.82.120.139 port 48362 ssh2
Feb  5 03:14:44 HOST sshd[19542]: Received disconnect from 183.82.120.139: 11: Bye Bye [preauth]
Feb  5 03:17:51 HOST sshd[19699]: reveeclipse mapping checking getaddrinfo for broadband.actcorp.in [183.82.120.139] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  5 03:17:53 HOST sshd[19699]: Failed password for invalid user hsn from 183.82.120.139 port 50028 ssh2
Feb  5 03:17:53 HOST sshd[19699]: Received disconnect from 183.82.120.139: 11: Bye Bye [preauth]
Feb  5 03:21:11 HOST sshd[19829]: reveeclipse mapping checking ........
-------------------------------
2020-02-07 22:53:17
187.141.128.42 attackbots
2020-02-07T09:08:22.092644vostok sshd\[17783\]: Invalid user shd from 187.141.128.42 port 35932 | Triggered by Fail2Ban at Vostok web server
2020-02-07 23:24:30
181.49.50.126 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-07 23:35:38
125.164.218.211 attackspam
Feb  7 15:09:16 odroid64 sshd\[20660\]: User ftp from 125.164.218.211 not allowed because not listed in AllowUsers
Feb  7 15:09:16 odroid64 sshd\[20660\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.164.218.211  user=ftp
...
2020-02-07 22:50:44
119.9.94.145 attack
Feb  7 14:53:40 web8 sshd\[23504\]: Invalid user nuw from 119.9.94.145
Feb  7 14:53:40 web8 sshd\[23504\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.9.94.145
Feb  7 14:53:42 web8 sshd\[23504\]: Failed password for invalid user nuw from 119.9.94.145 port 35342 ssh2
Feb  7 14:56:26 web8 sshd\[24906\]: Invalid user spn from 119.9.94.145
Feb  7 14:56:26 web8 sshd\[24906\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.9.94.145
2020-02-07 23:03:32
163.179.54.199 attackspam
ICMP MH Probe, Scan /Distributed -
2020-02-07 23:25:07
169.45.77.194 attackspam
ICMP MH Probe, Scan /Distributed -
2020-02-07 23:17:08
1.162.144.20 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-07 23:09:41
36.78.201.122 attack
Feb  7 14:51:30 hcbbdb sshd\[13618\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.78.201.122  user=root
Feb  7 14:51:32 hcbbdb sshd\[13618\]: Failed password for root from 36.78.201.122 port 26922 ssh2
Feb  7 14:51:48 hcbbdb sshd\[13625\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.78.201.122  user=root
Feb  7 14:51:50 hcbbdb sshd\[13625\]: Failed password for root from 36.78.201.122 port 36799 ssh2
Feb  7 14:52:07 hcbbdb sshd\[13652\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.78.201.122  user=root
2020-02-07 23:08:17
190.109.64.92 attack
Automatic report - Port Scan Attack
2020-02-07 23:22:37
39.117.139.244 attackbotsspam
Feb  7 15:08:57 * sshd[2351]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.117.139.244
Feb  7 15:09:00 * sshd[2351]: Failed password for invalid user uyy from 39.117.139.244 port 38128 ssh2
2020-02-07 23:07:45
169.56.73.239 attackspambots
ICMP MH Probe, Scan /Distributed -
2020-02-07 22:56:47
213.150.209.178 attackspam
ZA_RIPE-NCC-HM-MNT_<177>1581084555 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2] {TCP} 213.150.209.178:54384
2020-02-07 22:50:09

Recently Reported IPs

120.32.154.129 98.204.64.224 221.195.110.204 60.97.45.219
39.216.145.201 161.244.233.197 144.217.36.73 227.63.62.159
98.54.19.239 62.223.84.35 204.54.134.224 113.71.22.144
18.153.151.185 137.133.45.38 63.115.192.157 6.41.154.231
153.62.117.252 204.79.163.5 201.147.207.42 149.13.232.221