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: United States

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

;; QUESTION SECTION:
;55.202.34.144.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 09:00:25 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 144.34.202.55.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 55.202.34.144.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
49.233.46.219 attackbots
$f2bV_matches
2020-04-30 04:16:06
213.217.0.134 attackbotsspam
Apr 29 22:35:49 debian-2gb-nbg1-2 kernel: \[10451469.587535\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=213.217.0.134 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=47072 PROTO=TCP SPT=58392 DPT=63224 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-30 04:38:20
222.186.175.154 attackspambots
DATE:2020-04-29 22:29:56, IP:222.186.175.154, PORT:ssh SSH brute force auth on honeypot server (epe-honey1-hq)
2020-04-30 04:40:41
190.103.31.30 attackspam
Unauthorized connection attempt from IP address 190.103.31.30 on Port 445(SMB)
2020-04-30 04:36:02
191.5.66.99 attackbotsspam
Unauthorized connection attempt from IP address 191.5.66.99 on Port 445(SMB)
2020-04-30 04:27:25
46.188.72.27 attackspambots
Apr 29 21:24:10 host5 sshd[8727]: Invalid user raghu from 46.188.72.27 port 46582
...
2020-04-30 04:18:28
206.189.147.137 attackbots
Apr 29 22:29:20 legacy sshd[19244]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.147.137
Apr 29 22:29:22 legacy sshd[19244]: Failed password for invalid user wms from 206.189.147.137 port 38200 ssh2
Apr 29 22:33:27 legacy sshd[19397]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.147.137
...
2020-04-30 04:42:48
47.74.245.246 attackspambots
SSH authentication failure x 6 reported by Fail2Ban
...
2020-04-30 04:18:06
89.42.252.124 attackbots
Invalid user ubuntu from 89.42.252.124 port 10188
2020-04-30 04:10:19
180.167.82.162 attackbotsspam
Unauthorized connection attempt from IP address 180.167.82.162 on Port 445(SMB)
2020-04-30 04:21:47
52.251.123.29 attack
Failed password for root from 52.251.123.29 port 54176 ssh2
2020-04-30 04:12:47
49.235.49.39 attackbots
2020-04-29T20:10:06.237644shield sshd\[29514\]: Invalid user meet from 49.235.49.39 port 57010
2020-04-29T20:10:06.241551shield sshd\[29514\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.49.39
2020-04-29T20:10:08.365669shield sshd\[29514\]: Failed password for invalid user meet from 49.235.49.39 port 57010 ssh2
2020-04-29T20:15:44.156074shield sshd\[30544\]: Invalid user fork from 49.235.49.39 port 33736
2020-04-29T20:15:44.159653shield sshd\[30544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.49.39
2020-04-30 04:35:51
104.168.44.166 attackbotsspam
Lines containing failures of 104.168.44.166
Apr 28 19:19:17 UTC__SANYALnet-Labs__cac12 sshd[9912]: Connection from 104.168.44.166 port 49337 on 64.137.176.96 port 22
Apr 28 19:19:17 UTC__SANYALnet-Labs__cac12 sshd[9912]: Did not receive identification string from 104.168.44.166 port 49337
Apr 28 19:19:21 UTC__SANYALnet-Labs__cac12 sshd[9913]: Connection from 104.168.44.166 port 52003 on 64.137.176.96 port 22
Apr 28 19:19:22 UTC__SANYALnet-Labs__cac12 sshd[9913]: Address 104.168.44.166 maps to 104-168-44-166-host.colocrossing.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Apr 28 19:19:22 UTC__SANYALnet-Labs__cac12 sshd[9913]: User r.r from 104.168.44.166 not allowed because not listed in AllowUsers
Apr 28 19:19:22 UTC__SANYALnet-Labs__cac12 sshd[9913]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.168.44.166  user=r.r
Apr 28 19:19:24 UTC__SANYALnet-Labs__cac12 sshd[9913]: Failed password for invali........
------------------------------
2020-04-30 04:08:35
95.24.21.33 attackbots
Unauthorized connection attempt from IP address 95.24.21.33 on Port 445(SMB)
2020-04-30 04:44:03
113.246.49.36 attack
GPON Home Routers Remote Code Execution Vulnerability
2020-04-30 04:32:12

Recently Reported IPs

167.149.63.168 219.135.205.38 29.144.48.33 47.114.69.76
74.2.24.239 172.214.105.145 5.112.152.197 36.93.73.174
231.38.186.149 39.52.170.6 187.83.85.102 218.208.22.156
224.247.131.46 136.252.212.14 175.14.219.153 203.6.184.231
4.181.241.237 25.203.153.247 123.101.93.171 101.129.90.52