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

;; QUESTION SECTION:
;104.22.2.201.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 12:17:34 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 201.2.22.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 201.2.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
73.234.56.218 attack
Unauthorized connection attempt detected from IP address 73.234.56.218 to port 23
2020-06-17 18:45:26
125.227.26.21 attackspambots
Invalid user ubuntu from 125.227.26.21 port 57442
2020-06-17 18:59:42
118.25.44.66 attackspambots
Invalid user nagios from 118.25.44.66 port 37736
2020-06-17 18:54:31
171.252.130.186 attackspambots
20/6/16@23:48:14: FAIL: Alarm-Network address from=171.252.130.186
20/6/16@23:48:14: FAIL: Alarm-Network address from=171.252.130.186
...
2020-06-17 19:15:34
91.136.153.229 attackbotsspam
Tried our host z.
2020-06-17 19:12:57
186.248.175.137 attackbotsspam
Unauthorized IMAP connection attempt
2020-06-17 19:07:01
180.76.245.228 attackspam
Jun 17 07:55:03 sso sshd[27489]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.245.228
Jun 17 07:55:05 sso sshd[27489]: Failed password for invalid user admin from 180.76.245.228 port 34420 ssh2
...
2020-06-17 18:39:46
103.133.114.6 attackbots
/cms/wp-login.php
2020-06-17 19:00:06
3.34.141.94 attack
Invalid user eth from 3.34.141.94 port 41048
2020-06-17 19:03:09
42.159.121.246 attackbots
Jun 17 11:35:11 ns3164893 sshd[10938]: Failed password for root from 42.159.121.246 port 42140 ssh2
Jun 17 11:48:03 ns3164893 sshd[11091]: Invalid user lizhen from 42.159.121.246 port 60040
...
2020-06-17 18:38:42
185.176.27.30 attack
Jun 17 13:00:45 debian-2gb-nbg1-2 kernel: \[14650343.986557\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.30 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=48247 PROTO=TCP SPT=49741 DPT=24384 WINDOW=1024 RES=0x00 SYN URGP=0
2020-06-17 19:10:26
36.133.38.45 attack
SSH brute-force attempt
2020-06-17 18:58:13
148.70.230.63 attack
Jun 17 07:39:06 journals sshd\[118580\]: Invalid user pgsql from 148.70.230.63
Jun 17 07:39:06 journals sshd\[118580\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.230.63
Jun 17 07:39:08 journals sshd\[118580\]: Failed password for invalid user pgsql from 148.70.230.63 port 38740 ssh2
Jun 17 07:45:17 journals sshd\[119295\]: Invalid user morita from 148.70.230.63
Jun 17 07:45:17 journals sshd\[119295\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.230.63
...
2020-06-17 18:40:06
162.243.143.193 attack
" "
2020-06-17 19:09:57
134.119.192.227 attackbots
 TCP (SYN) 134.119.192.227:36410 -> port 22, len 48
2020-06-17 19:01:36

Recently Reported IPs

104.22.2.127 104.22.2.194 104.22.20.164 104.22.2.160
104.248.103.35 104.22.2.228 104.22.2.91 104.22.2.93
104.22.20.226 104.22.21.164 144.96.193.234 104.22.21.226
104.22.22.126 104.22.22.105 104.22.21.69 104.22.20.69
1.230.110.19 104.254.244.19 193.200.123.43 104.254.244.24