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

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

;; QUESTION SECTION:
;185.104.45.53.			IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 19 03:56:35 CST 2022
;; MSG SIZE  rcvd: 106
Host info
53.45.104.185.in-addr.arpa domain name pointer web661.default-host.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
53.45.104.185.in-addr.arpa	name = web661.default-host.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
125.224.210.98 attackbots
firewall-block, port(s): 23/tcp
2020-02-01 15:00:10
139.59.4.224 attackspambots
Unauthorized connection attempt detected from IP address 139.59.4.224 to port 2220 [J]
2020-02-01 14:45:11
31.28.41.185 attack
Automatic report - Port Scan Attack
2020-02-01 14:57:18
1.220.46.99 attackbots
Invalid user admin from 1.220.46.99 port 33386
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.220.46.99
Failed password for invalid user admin from 1.220.46.99 port 33386 ssh2
Invalid user admin from 1.220.46.99 port 33393
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.220.46.99
2020-02-01 15:17:49
200.127.21.133 attackbotsspam
Feb  1 11:00:30 gw1 sshd[5094]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.127.21.133
Feb  1 11:00:32 gw1 sshd[5094]: Failed password for invalid user ts3srv from 200.127.21.133 port 43016 ssh2
...
2020-02-01 14:50:39
219.84.229.101 attackspambots
20/1/31@23:55:59: FAIL: Alarm-Network address from=219.84.229.101
...
2020-02-01 15:00:28
51.79.25.38 attack
$f2bV_matches
2020-02-01 15:10:17
49.234.206.45 attackspambots
Feb  1 07:19:18 legacy sshd[5873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.206.45
Feb  1 07:19:20 legacy sshd[5873]: Failed password for invalid user arkserver from 49.234.206.45 port 36638 ssh2
Feb  1 07:23:35 legacy sshd[6083]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.206.45
...
2020-02-01 15:15:19
222.186.30.248 attackspam
Feb  1 07:29:31 v22018076622670303 sshd\[32486\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.248  user=root
Feb  1 07:29:33 v22018076622670303 sshd\[32486\]: Failed password for root from 222.186.30.248 port 56761 ssh2
Feb  1 07:29:36 v22018076622670303 sshd\[32486\]: Failed password for root from 222.186.30.248 port 56761 ssh2
...
2020-02-01 15:07:23
194.55.185.63 attackspam
FROM MAYAK CONSULTING
2020-02-01 15:12:55
84.3.122.229 attackbotsspam
Feb  1 05:50:13 DAAP sshd[22815]: Invalid user ts3server from 84.3.122.229 port 42952
Feb  1 05:50:13 DAAP sshd[22815]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.3.122.229
Feb  1 05:50:13 DAAP sshd[22815]: Invalid user ts3server from 84.3.122.229 port 42952
Feb  1 05:50:16 DAAP sshd[22815]: Failed password for invalid user ts3server from 84.3.122.229 port 42952 ssh2
Feb  1 05:55:52 DAAP sshd[22850]: Invalid user sammy from 84.3.122.229 port 56928
...
2020-02-01 15:05:58
222.186.42.7 attackbots
2020-02-01T01:28:36.388813vostok sshd\[31240\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.7  user=root | Triggered by Fail2Ban at Vostok web server
2020-02-01 14:54:57
221.194.44.156 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-02-01 15:01:23
49.88.112.114 attack
Feb  1 07:26:05 OPSO sshd\[10488\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
Feb  1 07:26:07 OPSO sshd\[10488\]: Failed password for root from 49.88.112.114 port 47930 ssh2
Feb  1 07:26:09 OPSO sshd\[10488\]: Failed password for root from 49.88.112.114 port 47930 ssh2
Feb  1 07:26:12 OPSO sshd\[10488\]: Failed password for root from 49.88.112.114 port 47930 ssh2
Feb  1 07:27:02 OPSO sshd\[10490\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
2020-02-01 14:53:59
176.199.47.186 attackspam
Invalid user akanksha from 176.199.47.186 port 60086
2020-02-01 14:43:00

Recently Reported IPs

185.104.45.45 185.104.45.59 185.104.45.86 185.105.184.75
185.105.109.12 185.105.184.84 185.105.185.172 185.105.186.56
185.105.187.27 185.105.103.150 185.105.226.184 185.106.128.101
185.106.128.242 185.106.208.202 185.106.208.35 185.106.209.76
185.106.210.226 185.105.237.219 185.106.209.85 185.106.210.175