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

;; QUESTION SECTION:
;104.164.122.196.		IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 21 18:00:38 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 196.122.164.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 196.122.164.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
103.135.39.192 attackspambots
Unauthorized connection attempt detected from IP address 103.135.39.192 to port 80 [J]
2020-02-04 05:45:31
101.234.76.77 attackspambots
Unauthorized connection attempt detected from IP address 101.234.76.77 to port 1433 [J]
2020-02-04 05:46:24
189.253.158.240 attackspambots
Unauthorized connection attempt detected from IP address 189.253.158.240 to port 81 [J]
2020-02-04 05:36:38
122.117.91.130 attackbotsspam
Unauthorized connection attempt detected from IP address 122.117.91.130 to port 23 [J]
2020-02-04 05:22:47
190.175.33.104 attackspambots
Unauthorized connection attempt detected from IP address 190.175.33.104 to port 23 [J]
2020-02-04 05:35:55
186.249.195.183 attack
Unauthorized connection attempt detected from IP address 186.249.195.183 to port 81 [J]
2020-02-04 05:14:49
1.54.245.139 attackspam
Unauthorized connection attempt detected from IP address 1.54.245.139 to port 23 [J]
2020-02-04 05:11:46
3.87.225.158 attackspam
Unauthorized connection attempt detected from IP address 3.87.225.158 to port 22 [J]
2020-02-04 05:11:21
120.24.244.15 attackbotsspam
Unauthorized connection attempt detected from IP address 120.24.244.15 to port 8545 [J]
2020-02-04 05:43:49
36.74.67.118 attackbots
Unauthorized connection attempt detected from IP address 36.74.67.118 to port 80 [J]
2020-02-04 05:10:25
106.12.52.98 attack
Unauthorized connection attempt detected from IP address 106.12.52.98 to port 2220 [J]
2020-02-04 05:25:41
103.44.27.58 attack
Unauthorized connection attempt detected from IP address 103.44.27.58 to port 2220 [J]
2020-02-04 05:46:05
185.56.153.229 attackspam
Unauthorized connection attempt detected from IP address 185.56.153.229 to port 2220 [J]
2020-02-04 05:15:50
113.172.227.105 attackbotsspam
Unauthorized connection attempt detected from IP address 113.172.227.105 to port 22 [J]
2020-02-04 05:24:01
67.205.153.16 attackspambots
Feb  3 22:14:10 dedicated sshd[2140]: Invalid user tom from 67.205.153.16 port 34060
Feb  3 22:14:10 dedicated sshd[2140]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.153.16 
Feb  3 22:14:10 dedicated sshd[2140]: Invalid user tom from 67.205.153.16 port 34060
Feb  3 22:14:12 dedicated sshd[2140]: Failed password for invalid user tom from 67.205.153.16 port 34060 ssh2
Feb  3 22:18:55 dedicated sshd[3130]: Invalid user developer from 67.205.153.16 port 58740
2020-02-04 05:29:45

Recently Reported IPs

104.164.122.195 104.164.122.198 104.164.122.199 104.164.122.200
104.164.122.239 104.164.122.240 104.164.122.241 104.164.122.242
104.164.122.243 104.164.122.244 104.164.167.144 104.164.192.19
104.164.192.20 104.164.192.21 104.164.192.22 104.164.192.23
104.164.192.239 104.164.192.240 104.164.192.241 104.164.192.248