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

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

;; QUESTION SECTION:
;55.159.104.77.			IN	A

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

;; Query time: 109 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 11 12:16:07 CST 2022
;; MSG SIZE  rcvd: 106
Host info
b'Host 77.104.159.55.in-addr.arpa. not found: 3(NXDOMAIN)
'
Nslookup info:
server can't find 55.159.104.77.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
203.189.252.138 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-03 21:32:15
14.186.191.97 attackspambots
Autoban   14.186.191.97 ABORTED AUTH
2019-12-03 22:00:40
20.188.4.3 attackbotsspam
2019-12-03T11:10:21.939367struts4.enskede.local sshd\[22714\]: Invalid user foulkes from 20.188.4.3 port 59116
2019-12-03T11:10:21.947200struts4.enskede.local sshd\[22714\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=20.188.4.3
2019-12-03T11:10:25.187588struts4.enskede.local sshd\[22714\]: Failed password for invalid user foulkes from 20.188.4.3 port 59116 ssh2
2019-12-03T11:16:55.800754struts4.enskede.local sshd\[22736\]: Invalid user montaldo from 20.188.4.3 port 44342
2019-12-03T11:16:55.807637struts4.enskede.local sshd\[22736\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=20.188.4.3
...
2019-12-03 21:29:41
139.59.171.46 attack
fail2ban honeypot
2019-12-03 21:46:18
162.244.95.2 attackbotsspam
Wordpress login scanning
2019-12-03 22:02:13
85.186.25.135 attackbots
Automatic report - Port Scan Attack
2019-12-03 21:59:19
159.89.134.64 attackbotsspam
Dec  2 13:50:09 server sshd\[32103\]: Failed password for invalid user mulkerin from 159.89.134.64 port 60748 ssh2
Dec  3 09:16:48 server sshd\[27040\]: Invalid user bacco from 159.89.134.64
Dec  3 09:16:48 server sshd\[27040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.134.64 
Dec  3 09:16:50 server sshd\[27040\]: Failed password for invalid user bacco from 159.89.134.64 port 44298 ssh2
Dec  3 09:22:24 server sshd\[28457\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.134.64  user=lp
...
2019-12-03 22:04:04
106.13.49.233 attackspam
Dec  3 10:33:16 firewall sshd[19409]: Failed password for invalid user pcap from 106.13.49.233 port 32882 ssh2
Dec  3 10:41:20 firewall sshd[19669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.49.233  user=root
Dec  3 10:41:22 firewall sshd[19669]: Failed password for root from 106.13.49.233 port 58594 ssh2
...
2019-12-03 21:44:22
77.43.190.232 attackspambots
Dec  3 07:02:28 mail1 sshd[658]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.43.190.232  user=r.r
Dec  3 07:02:30 mail1 sshd[658]: Failed password for r.r from 77.43.190.232 port 46225 ssh2
Dec  3 07:02:32 mail1 sshd[658]: Failed password for r.r from 77.43.190.232 port 46225 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=77.43.190.232
2019-12-03 21:59:38
139.199.158.14 attack
SSH auth scanning - multiple failed logins
2019-12-03 21:36:13
218.78.54.80 attack
2019-12-03 07:37:06,220 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 218.78.54.80
2019-12-03 08:11:54,467 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 218.78.54.80
2019-12-03 08:56:07,212 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 218.78.54.80
2019-12-03 09:31:49,958 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 218.78.54.80
2019-12-03 10:03:35,918 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 218.78.54.80
...
2019-12-03 22:01:08
222.92.139.158 attack
Dec  3 02:01:01 TORMINT sshd\[26956\]: Invalid user dbus from 222.92.139.158
Dec  3 02:01:01 TORMINT sshd\[26956\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.92.139.158
Dec  3 02:01:04 TORMINT sshd\[26956\]: Failed password for invalid user dbus from 222.92.139.158 port 41932 ssh2
...
2019-12-03 21:57:42
128.199.90.245 attack
SSH bruteforce (Triggered fail2ban)
2019-12-03 21:32:34
47.17.177.110 attackbotsspam
Dec  3 13:58:03 legacy sshd[19922]: Failed password for root from 47.17.177.110 port 54480 ssh2
Dec  3 14:07:45 legacy sshd[20329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.17.177.110
Dec  3 14:07:47 legacy sshd[20329]: Failed password for invalid user heleen from 47.17.177.110 port 37896 ssh2
...
2019-12-03 21:43:08
52.130.66.9 attackspambots
Dec  3 07:22:35 raspberrypi sshd\[30886\]: Did not receive identification string from 52.130.66.9
...
2019-12-03 21:55:40

Recently Reported IPs

139.129.142.128 141.115.26.254 35.0.157.11 32.223.203.114
157.88.255.100 130.181.201.68 29.85.207.63 82.234.54.98
224.141.127.191 8.184.38.197 124.16.112.251 197.16.96.24
3.205.173.135 125.103.241.226 177.61.58.24 139.182.158.174
185.40.28.167 10.144.10.62 223.153.190.51 201.244.199.69