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

;; QUESTION SECTION:
;77.180.149.55.			IN	A

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

;; Query time: 84 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Dec 08 15:51:45 CST 2024
;; MSG SIZE  rcvd: 106
Host info
55.149.180.77.in-addr.arpa domain name pointer dynamic-077-180-149-055.77.180.pool.telefonica.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
55.149.180.77.in-addr.arpa	name = dynamic-077-180-149-055.77.180.pool.telefonica.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
178.128.124.106 attackbotsspam
loopsrockreggae.com 178.128.124.106 \[02/Nov/2019:21:19:39 +0100\] "POST /wp-login.php HTTP/1.1" 200 5613 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
loopsrockreggae.com 178.128.124.106 \[02/Nov/2019:21:19:41 +0100\] "POST /wp-login.php HTTP/1.1" 200 5581 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-03 05:13:14
134.175.46.166 attackbotsspam
Nov  2 21:53:43 lnxded63 sshd[16806]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.46.166
Nov  2 21:53:43 lnxded63 sshd[16806]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.46.166
2019-11-03 05:13:45
49.88.112.111 attackspambots
Nov  3 01:41:00 gw1 sshd[6022]: Failed password for root from 49.88.112.111 port 31672 ssh2
...
2019-11-03 05:00:41
114.214.164.141 attack
Connection by 114.214.164.141 on port: 23 got caught by honeypot at 11/2/2019 8:20:19 PM
2019-11-03 04:51:40
41.214.138.178 attack
Nov  2 21:11:24 localhost sshd\[5382\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.214.138.178  user=root
Nov  2 21:11:26 localhost sshd\[5382\]: Failed password for root from 41.214.138.178 port 60298 ssh2
Nov  2 21:15:23 localhost sshd\[5605\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.214.138.178  user=root
Nov  2 21:15:25 localhost sshd\[5605\]: Failed password for root from 41.214.138.178 port 41704 ssh2
Nov  2 21:19:17 localhost sshd\[5692\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.214.138.178  user=root
...
2019-11-03 05:26:34
212.129.145.24 attackbots
Nov  2 10:50:59 hanapaa sshd\[16114\]: Invalid user Link@123 from 212.129.145.24
Nov  2 10:50:59 hanapaa sshd\[16114\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.129.145.24
Nov  2 10:51:01 hanapaa sshd\[16114\]: Failed password for invalid user Link@123 from 212.129.145.24 port 36440 ssh2
Nov  2 10:55:30 hanapaa sshd\[16447\]: Invalid user ktjb4sh3 from 212.129.145.24
Nov  2 10:55:30 hanapaa sshd\[16447\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.129.145.24
2019-11-03 05:21:48
170.150.155.102 attack
Nov  2 21:32:29 meumeu sshd[539]: Failed password for root from 170.150.155.102 port 45752 ssh2
Nov  2 21:36:53 meumeu sshd[1312]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.150.155.102 
Nov  2 21:36:55 meumeu sshd[1312]: Failed password for invalid user lv from 170.150.155.102 port 55834 ssh2
...
2019-11-03 05:14:00
187.32.18.208 attackspam
Automatic report - Port Scan Attack
2019-11-03 04:58:00
106.12.85.76 attackbots
Nov  2 21:19:42 * sshd[17960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.85.76
Nov  2 21:19:44 * sshd[17960]: Failed password for invalid user admin from 106.12.85.76 port 45962 ssh2
2019-11-03 05:10:02
134.175.121.31 attack
Nov  2 10:47:41 eddieflores sshd\[23025\]: Invalid user rudy from 134.175.121.31
Nov  2 10:47:41 eddieflores sshd\[23025\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.121.31
Nov  2 10:47:44 eddieflores sshd\[23025\]: Failed password for invalid user rudy from 134.175.121.31 port 55345 ssh2
Nov  2 10:51:37 eddieflores sshd\[23302\]: Invalid user bluesun from 134.175.121.31
Nov  2 10:51:37 eddieflores sshd\[23302\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.121.31
2019-11-03 05:12:09
80.211.231.224 attackbotsspam
Nov  2 13:39:03 mockhub sshd[25048]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.231.224
Nov  2 13:39:05 mockhub sshd[25048]: Failed password for invalid user postgres from 80.211.231.224 port 60376 ssh2
...
2019-11-03 04:49:43
106.13.12.76 attackspambots
Automatic report - Banned IP Access
2019-11-03 05:15:37
222.186.173.238 attack
DATE:2019-11-02 22:13:59, IP:222.186.173.238, PORT:ssh SSH brute force auth on honeypot server (honey-neo-dc-bis)
2019-11-03 05:28:21
112.16.169.101 attackspambots
Fail2Ban Ban Triggered
2019-11-03 05:23:57
110.136.94.199 attack
" "
2019-11-03 05:17:55

Recently Reported IPs

215.202.60.24 82.153.15.124 146.55.195.1 20.253.60.252
193.7.30.197 232.19.237.111 198.209.165.172 90.138.101.242
74.141.6.249 116.108.181.200 39.176.86.246 46.169.49.29
200.55.39.187 189.110.233.95 78.52.157.155 156.108.242.243
8.163.146.196 65.47.81.81 84.152.113.247 249.75.51.204