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

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

;; QUESTION SECTION:
;104.144.134.16.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 26 00:40:17 CST 2022
;; MSG SIZE  rcvd: 107
Host info
16.134.144.104.in-addr.arpa domain name pointer 74f53.percentraliasrity.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
16.134.144.104.in-addr.arpa	name = 74f53.percentraliasrity.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
217.61.20.142 attackspam
Feb  3 20:27:43 debian-2gb-nbg1-2 kernel: \[3017315.087036\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=217.61.20.142 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=54321 PROTO=TCP SPT=46635 DPT=81 WINDOW=65535 RES=0x00 SYN URGP=0
2020-02-04 03:38:54
24.224.141.197 attackspambots
Unauthorized connection attempt detected from IP address 24.224.141.197 to port 5555 [J]
2020-02-04 04:00:16
170.106.36.31 attackbotsspam
Unauthorized connection attempt detected from IP address 170.106.36.31 to port 505 [J]
2020-02-04 03:44:28
91.244.114.135 attackbots
Unauthorized connection attempt detected from IP address 91.244.114.135 to port 80 [J]
2020-02-04 03:29:05
91.121.116.65 attackspambots
Unauthorized connection attempt detected from IP address 91.121.116.65 to port 2220 [J]
2020-02-04 03:29:33
119.207.195.52 attackspam
Unauthorized connection attempt detected from IP address 119.207.195.52 to port 23 [J]
2020-02-04 03:49:01
45.143.137.41 attackbots
Unauthorized connection attempt detected from IP address 45.143.137.41 to port 80 [J]
2020-02-04 03:33:55
123.20.176.23 attackbots
Unauthorized connection attempt detected from IP address 123.20.176.23 to port 22 [J]
2020-02-04 03:47:28
45.114.83.248 attackbotsspam
Unauthorized connection attempt detected from IP address 45.114.83.248 to port 3389 [J]
2020-02-04 03:34:13
210.86.170.118 attackbotsspam
Unauthorized connection attempt detected from IP address 210.86.170.118 to port 22 [J]
2020-02-04 03:40:03
91.232.159.155 attackspambots
Unauthorized connection attempt detected from IP address 91.232.159.155 to port 80 [J]
2020-02-04 03:55:00
187.162.126.105 attackbots
Unauthorized connection attempt detected from IP address 187.162.126.105 to port 23 [J]
2020-02-04 03:42:36
130.61.51.92 attackbots
21 attempts against mh-ssh on echoip
2020-02-04 03:46:02
103.43.123.231 attackbots
Unauthorized connection attempt detected from IP address 103.43.123.231 to port 23 [J]
2020-02-04 03:53:17
121.179.232.246 attack
Unauthorized connection attempt detected from IP address 121.179.232.246 to port 81 [J]
2020-02-04 03:48:11

Recently Reported IPs

104.144.134.155 103.205.58.13 104.144.134.142 104.144.134.139
104.144.134.171 104.144.134.185 103.205.58.143 104.144.134.196
104.144.134.21 104.144.134.192 104.144.134.212 104.144.134.231
104.144.134.247 104.144.134.195 104.144.134.221 104.144.134.248
104.144.134.25 204.77.173.91 104.144.134.33 104.144.134.29