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: Netherlands (the)

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

;; QUESTION SECTION:
;144.54.36.55.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 02 05:22:57 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 55.36.54.144.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 55.36.54.144.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
124.115.21.51 attack
Jan 29 11:36:25 firewall sshd[9814]: Invalid user syama from 124.115.21.51
Jan 29 11:36:27 firewall sshd[9814]: Failed password for invalid user syama from 124.115.21.51 port 63847 ssh2
Jan 29 11:38:56 firewall sshd[9899]: Invalid user nawang from 124.115.21.51
...
2020-01-29 23:42:12
89.248.162.136 attackbots
01/29/2020-16:27:51.931579 89.248.162.136 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 99
2020-01-29 23:38:03
185.176.27.6 attack
Jan 29 16:59:52 debian-2gb-nbg1-2 kernel: \[2572856.144082\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.6 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=33844 PROTO=TCP SPT=45132 DPT=9533 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-30 00:01:24
104.206.128.62 attack
Unauthorized connection attempt detected from IP address 104.206.128.62 to port 3389 [J]
2020-01-29 23:42:45
18.231.150.170 attackbotsspam
/.git (404)
2020-01-29 23:51:05
200.69.82.186 attack
2019-03-08 15:43:09 1h2GiK-0005cZ-EA SMTP connection from \(azteca-comunicaciones.com\) \[200.69.82.186\]:1869 I=\[193.107.88.166\]:25 closed by DROP in ACL
2019-03-08 15:44:11 1h2GjK-0005dw-AQ SMTP connection from \(azteca-comunicaciones.com\) \[200.69.82.186\]:46284 I=\[193.107.88.166\]:25 closed by DROP in ACL
2019-03-08 15:44:41 1h2Gjo-0005eh-KG SMTP connection from \(azteca-comunicaciones.com\) \[200.69.82.186\]:46476 I=\[193.107.88.166\]:25 closed by DROP in ACL
...
2020-01-29 23:35:01
200.69.250.253 attackspam
"Fail2Ban detected SSH brute force attempt"
2020-01-29 23:23:24
106.12.220.156 attackbots
Jan 29 08:01:00 mail sshd[7338]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.220.156 
Jan 29 08:01:03 mail sshd[7338]: Failed password for invalid user takashima from 106.12.220.156 port 35898 ssh2
Jan 29 08:08:43 mail sshd[8481]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.220.156
2020-01-30 00:06:49
108.185.125.240 attack
Automatic report - Port Scan Attack
2020-01-29 23:39:42
200.69.68.245 attackbotsspam
2019-10-23 17:48:34 1iNIs4-0000bR-N1 SMTP connection from \(azteca-comunicaciones.com\) \[200.69.68.245\]:11966 I=\[193.107.88.166\]:25 closed by DROP in ACL
2019-10-23 17:49:51 1iNItM-0000dJ-26 SMTP connection from \(azteca-comunicaciones.com\) \[200.69.68.245\]:11912 I=\[193.107.88.166\]:25 closed by DROP in ACL
2019-10-23 17:51:07 1iNIuN-0000gM-Gi SMTP connection from \(azteca-comunicaciones.com\) \[200.69.68.245\]:11952 I=\[193.107.88.166\]:25 closed by DROP in ACL
...
2020-01-29 23:36:49
45.132.87.180 attackspambots
1580304877 - 01/29/2020 14:34:37 Host: 45.132.87.180/45.132.87.180 Port: 445 TCP Blocked
2020-01-29 23:24:15
200.68.113.130 attackspam
2019-03-11 15:35:04 H=\(h113-130.sslil.com\) \[200.68.113.130\]:38010 I=\[193.107.88.166\]:25 F=\ rejected RCPT \: Sender verify failed
2019-03-11 15:35:05 H=\(h113-130.sslil.com\) \[200.68.113.130\]:38041 I=\[193.107.88.166\]:25 F=\ rejected RCPT \: Sender verify failed
2019-03-11 15:35:07 H=\(h113-130.sslil.com\) \[200.68.113.130\]:38052 I=\[193.107.88.166\]:25 F=\ rejected RCPT \: Sender verify failed
...
2020-01-29 23:44:33
90.143.21.17 attackbotsspam
20/1/29@08:34:10: FAIL: Alarm-Network address from=90.143.21.17
...
2020-01-30 00:04:10
182.253.226.212 attack
Jan 29 16:35:49 meumeu sshd[18374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.253.226.212 
Jan 29 16:35:50 meumeu sshd[18374]: Failed password for invalid user tami from 182.253.226.212 port 51965 ssh2
Jan 29 16:40:25 meumeu sshd[19049]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.253.226.212 
...
2020-01-29 23:43:52
81.245.109.108 attack
Jan 29 16:35:00 meumeu sshd[18244]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.245.109.108 
Jan 29 16:35:01 meumeu sshd[18244]: Failed password for invalid user dyutikara from 81.245.109.108 port 51402 ssh2
Jan 29 16:37:45 meumeu sshd[18628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.245.109.108 
...
2020-01-29 23:49:51

Recently Reported IPs

172.106.152.47 100.254.167.226 7.160.127.229 22.61.211.80
57.198.200.197 202.50.66.234 200.36.37.48 116.49.46.83
96.209.62.204 130.106.133.123 162.113.101.220 143.162.219.87
115.124.203.232 39.51.230.242 145.60.27.32 230.190.94.176
244.183.13.1 85.70.98.144 207.113.83.33 254.180.45.172