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

;; QUESTION SECTION:
;104.22.68.131.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:43:23 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 131.68.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 131.68.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
91.134.134.21 attackspambots
Jul  8 20:36:47 tuxlinux sshd[49454]: Invalid user cdc from 91.134.134.21 port 48388
Jul  8 20:36:47 tuxlinux sshd[49454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.134.21 
Jul  8 20:36:47 tuxlinux sshd[49454]: Invalid user cdc from 91.134.134.21 port 48388
Jul  8 20:36:47 tuxlinux sshd[49454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.134.21 
Jul  8 20:36:47 tuxlinux sshd[49454]: Invalid user cdc from 91.134.134.21 port 48388
Jul  8 20:36:47 tuxlinux sshd[49454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.134.21 
Jul  8 20:36:48 tuxlinux sshd[49454]: Failed password for invalid user cdc from 91.134.134.21 port 48388 ssh2
...
2019-07-09 08:26:45
93.62.39.108 attack
blogonese.net 93.62.39.108 \[09/Jul/2019:02:01:59 +0200\] "POST /wp-login.php HTTP/1.1" 200 5771 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
blogonese.net 93.62.39.108 \[09/Jul/2019:02:02:00 +0200\] "POST /wp-login.php HTTP/1.1" 200 5731 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
blogonese.net 93.62.39.108 \[09/Jul/2019:02:02:01 +0200\] "POST /wp-login.php HTTP/1.1" 200 5732 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-07-09 08:12:18
209.141.36.138 attack
Blocked for port scanning.
Time: Mon Jul 8. 07:47:55 2019 +0200
IP: 209.141.36.138 (US/United States/-)

Sample of block hits:
Jul 8 07:45:06 vserv kernel: [12205549.003541] Firewall: *TCP_IN Blocked* IN=venet0 OUT= MAC= SRC=209.141.36.138 DST=[removed] LEN=44 TOS=0x08 PREC=0x20 TTL=245 ID=32314 PROTO=TCP SPT=44628 DPT=2080 WINDOW=1024 RES=0x00 SYN URGP=0
Jul 8 07:45:08 vserv kernel: [12205551.340650] Firewall: *TCP_IN Blocked* IN=venet0 OUT= MAC= SRC=209.141.36.138 DST=[removed] LEN=44 TOS=0x08 PREC=0x20 TTL=245 ID=8143 PROTO=TCP SPT=44628 DPT=5055 WINDOW=1024 RES=0x00 SYN URGP=0
Jul 8 07:45:18 vserv kernel: [12205561.498285] Firewall: *TCP_IN Blocked* IN=venet0 OUT= MAC= SRC=209.141.36.138 DST=[removed] LEN=44 TOS=0x08 PREC=0x20 TTL=245 ID=4731 PROTO=TCP SPT=44628 DPT=1515 WINDOW=1024 RES=0x00 SYN URGP=0
Jul 8 07:45:43 vserv kernel: [12205586.672109] Firewall: *TCP_IN Blocked* IN=venet0 OUT= MAC= SRC=209.141.36.138 DST=[removed] LEN=44 TOS=0x08 PREC=0x20 TTL=245 ID=13161 PROTO=TCP SPT=44628 DPT=8888
2019-07-09 08:08:35
159.203.122.149 attackbotsspam
$f2bV_matches
2019-07-09 08:31:53
51.79.64.101 attack
pillott.xyz (checking ip) = 51.79.64.101
2019-07-09 08:36:58
88.250.238.6 attack
TCP port 8080 (HTTP) attempt blocked by firewall. [2019-07-08 20:36:50]
2019-07-09 08:16:50
109.104.173.46 attack
Jul  9 01:21:01 mail sshd\[27948\]: Invalid user teamspeak from 109.104.173.46 port 60250
Jul  9 01:21:01 mail sshd\[27948\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.104.173.46
...
2019-07-09 08:34:01
122.228.19.80 attackbots
Automatic report - Web App Attack
2019-07-09 08:36:37
144.217.7.154 attackspam
Jul  9 00:08:45 vibhu-HP-Z238-Microtower-Workstation sshd\[13058\]: Invalid user admin from 144.217.7.154
Jul  9 00:08:45 vibhu-HP-Z238-Microtower-Workstation sshd\[13058\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.7.154
Jul  9 00:08:47 vibhu-HP-Z238-Microtower-Workstation sshd\[13058\]: Failed password for invalid user admin from 144.217.7.154 port 56066 ssh2
Jul  9 00:08:50 vibhu-HP-Z238-Microtower-Workstation sshd\[13058\]: Failed password for invalid user admin from 144.217.7.154 port 56066 ssh2
Jul  9 00:08:53 vibhu-HP-Z238-Microtower-Workstation sshd\[13058\]: Failed password for invalid user admin from 144.217.7.154 port 56066 ssh2
...
2019-07-09 07:54:26
156.208.160.42 attack
scan r
2019-07-09 08:00:14
181.49.219.114 attackspam
Jul  9 00:35:36 Proxmox sshd\[22719\]: Invalid user san from 181.49.219.114 port 43904
Jul  9 00:35:36 Proxmox sshd\[22719\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.49.219.114
Jul  9 00:35:37 Proxmox sshd\[22719\]: Failed password for invalid user san from 181.49.219.114 port 43904 ssh2
Jul  9 00:38:11 Proxmox sshd\[25110\]: Invalid user www from 181.49.219.114 port 55746
Jul  9 00:38:11 Proxmox sshd\[25110\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.49.219.114
Jul  9 00:38:13 Proxmox sshd\[25110\]: Failed password for invalid user www from 181.49.219.114 port 55746 ssh2
2019-07-09 08:20:41
185.234.216.105 attack
Jul  8 18:32:37 web1 postfix/smtpd[16990]: warning: unknown[185.234.216.105]: SASL LOGIN authentication failed: authentication failure
...
2019-07-09 07:58:27
192.144.151.30 attackspambots
2019-07-08T20:36:51.2419591240 sshd\[31459\]: Invalid user test from 192.144.151.30 port 57198
2019-07-08T20:36:51.2486721240 sshd\[31459\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.151.30
2019-07-08T20:36:53.5775481240 sshd\[31459\]: Failed password for invalid user test from 192.144.151.30 port 57198 ssh2
...
2019-07-09 08:25:29
120.92.104.116 attack
Jul  8 18:29:59 ip-172-31-1-72 sshd\[16857\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.92.104.116  user=root
Jul  8 18:30:00 ip-172-31-1-72 sshd\[16857\]: Failed password for root from 120.92.104.116 port 63620 ssh2
Jul  8 18:38:38 ip-172-31-1-72 sshd\[16922\]: Invalid user vbox from 120.92.104.116
Jul  8 18:38:38 ip-172-31-1-72 sshd\[16922\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.92.104.116
Jul  8 18:38:41 ip-172-31-1-72 sshd\[16922\]: Failed password for invalid user vbox from 120.92.104.116 port 17477 ssh2
2019-07-09 07:56:39
51.83.70.149 attackspambots
Jul  8 20:36:53 vps647732 sshd[28000]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.70.149
Jul  8 20:36:54 vps647732 sshd[28000]: Failed password for invalid user pokemon from 51.83.70.149 port 45134 ssh2
...
2019-07-09 08:26:06

Recently Reported IPs

104.22.68.123 104.22.68.121 104.22.68.138 104.22.68.136
104.22.68.142 104.22.68.109 104.22.68.143 104.22.68.144
104.22.68.145 104.22.68.152 104.22.68.154 104.22.68.158
104.22.68.162 104.22.68.147 104.22.68.150 104.22.68.170
104.22.68.176 104.22.68.163 104.22.68.183 104.22.68.182