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

;; QUESTION SECTION:
;104.22.2.44.			IN	A

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

;; Query time: 84 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 16 01:45:02 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 44.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 44.2.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
121.134.159.21 attackbotsspam
Aug  9 12:18:28 icinga sshd[8665]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.134.159.21
Aug  9 12:18:30 icinga sshd[8665]: Failed password for invalid user admin from 121.134.159.21 port 55534 ssh2
...
2019-08-09 20:07:54
160.153.147.136 attackbotsspam
xmlrpc attack
2019-08-09 20:07:18
80.211.7.157 attackspam
Aug  9 07:59:24 debian sshd\[9993\]: Invalid user mysql from 80.211.7.157 port 56693
Aug  9 07:59:24 debian sshd\[9993\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.7.157
...
2019-08-09 19:58:45
171.237.192.40 attackbotsspam
Automatic report - Port Scan Attack
2019-08-09 20:29:10
73.95.0.82 attackbotsspam
port scan and connect, tcp 22 (ssh)
2019-08-09 19:54:22
95.10.27.239 attack
22/tcp
[2019-08-09]1pkt
2019-08-09 19:51:26
124.132.40.85 attackbots
23/tcp
[2019-08-09]1pkt
2019-08-09 19:42:27
104.155.91.177 attack
Aug  9 08:54:44 v22019058497090703 sshd[5389]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.155.91.177
Aug  9 08:54:46 v22019058497090703 sshd[5389]: Failed password for invalid user hy from 104.155.91.177 port 51346 ssh2
Aug  9 08:59:09 v22019058497090703 sshd[5755]: Failed password for root from 104.155.91.177 port 45816 ssh2
...
2019-08-09 19:46:16
60.184.226.142 attackspambots
23/tcp
[2019-08-09]1pkt
2019-08-09 20:25:37
159.89.13.0 attack
Aug  9 09:48:35 dedicated sshd[3243]: Invalid user 123456 from 159.89.13.0 port 45520
2019-08-09 20:22:03
156.218.198.3 attack
port scan and connect, tcp 23 (telnet)
2019-08-09 19:53:34
186.47.86.75 attackspam
23/tcp
[2019-08-09]1pkt
2019-08-09 20:01:47
87.96.139.69 attack
23/tcp
[2019-08-09]1pkt
2019-08-09 20:08:18
124.127.132.22 attack
Aug  9 13:33:01 h2177944 sshd\[19363\]: Invalid user administrador from 124.127.132.22 port 55834
Aug  9 13:33:01 h2177944 sshd\[19363\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.127.132.22
Aug  9 13:33:03 h2177944 sshd\[19363\]: Failed password for invalid user administrador from 124.127.132.22 port 55834 ssh2
Aug  9 13:37:11 h2177944 sshd\[19414\]: Invalid user ansari from 124.127.132.22 port 43078
...
2019-08-09 20:26:28
37.1.204.92 attackbots
Looking for resource vulnerabilities
2019-08-09 19:51:42

Recently Reported IPs

104.22.2.123 104.22.20.119 104.22.21.119 146.63.91.237
104.22.22.213 104.22.22.65 104.22.23.213 104.22.24.167
104.22.24.186 104.22.24.225 104.22.25.106 204.41.212.121
40.176.138.229 104.22.25.118 104.22.25.124 104.22.25.139
104.22.25.167 104.22.25.186 35.5.209.183 104.22.25.225