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

;; QUESTION SECTION:
;104.22.13.97.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:25:12 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 97.13.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 97.13.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
154.221.31.118 attackbotsspam
SSH brutforce
2019-11-10 09:28:07
202.165.228.177 attackspambots
Nov 10 06:04:23 lnxmail61 sshd[26924]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.165.228.177
Nov 10 06:04:24 lnxmail61 sshd[26924]: Failed password for invalid user test from 202.165.228.177 port 44002 ssh2
Nov 10 06:08:47 lnxmail61 sshd[27500]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.165.228.177
2019-11-10 13:14:14
122.165.140.147 attackspam
2019-11-10T06:09:55.605631scmdmz1 sshd\[26522\]: Invalid user lifei520 from 122.165.140.147 port 50824
2019-11-10T06:09:55.608420scmdmz1 sshd\[26522\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.165.140.147
2019-11-10T06:09:58.164754scmdmz1 sshd\[26522\]: Failed password for invalid user lifei520 from 122.165.140.147 port 50824 ssh2
...
2019-11-10 13:13:21
89.248.174.3 attack
*Port Scan* detected from 89.248.174.3 (NL/Netherlands/security.criminalip.com). 4 hits in the last 125 seconds
2019-11-10 13:04:14
129.28.30.54 attackbotsspam
2019-11-10T02:05:34.730019scmdmz1 sshd\[7014\]: Invalid user user from 129.28.30.54 port 41134
2019-11-10T02:05:34.732704scmdmz1 sshd\[7014\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.30.54
2019-11-10T02:05:36.588384scmdmz1 sshd\[7014\]: Failed password for invalid user user from 129.28.30.54 port 41134 ssh2
...
2019-11-10 09:15:58
114.67.70.94 attackbotsspam
SSH invalid-user multiple login try
2019-11-10 13:08:24
109.104.105.115 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-10 13:08:59
141.98.80.100 attackspambots
Nov 10 06:06:48 andromeda postfix/smtpd\[49685\]: warning: unknown\[141.98.80.100\]: SASL PLAIN authentication failed: authentication failure
Nov 10 06:06:48 andromeda postfix/smtpd\[25284\]: warning: unknown\[141.98.80.100\]: SASL PLAIN authentication failed: authentication failure
Nov 10 06:06:49 andromeda postfix/smtpd\[25286\]: warning: unknown\[141.98.80.100\]: SASL PLAIN authentication failed: authentication failure
Nov 10 06:06:49 andromeda postfix/smtpd\[10700\]: warning: unknown\[141.98.80.100\]: SASL PLAIN authentication failed: authentication failure
Nov 10 06:06:55 andromeda postfix/smtpd\[17058\]: warning: unknown\[141.98.80.100\]: SASL PLAIN authentication failed: authentication failure
2019-11-10 13:07:49
77.42.119.189 attackspam
Automatic report - Port Scan Attack
2019-11-10 09:17:46
45.125.66.31 attackbots
\[2019-11-09 20:03:25\] SECURITY\[2634\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-11-09T20:03:25.077-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="40110848178599002",SessionID="0x7fdf2cd1cd48",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/45.125.66.31/51384",ACLName="no_extension_match"
\[2019-11-09 20:04:56\] SECURITY\[2634\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-11-09T20:04:56.453-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="40110948178599002",SessionID="0x7fdf2cd1cd48",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/45.125.66.31/57162",ACLName="no_extension_match"
\[2019-11-09 20:06:21\] SECURITY\[2634\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-11-09T20:06:21.811-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="40111048178599002",SessionID="0x7fdf2c003608",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/45.125.66.31/55491",ACLName="no_
2019-11-10 09:15:32
159.203.201.5 attackspambots
159.203.201.5 was recorded 5 times by 5 hosts attempting to connect to the following ports: 8088. Incident counter (4h, 24h, all-time): 5, 15, 25
2019-11-10 13:20:58
104.236.45.171 attackbots
WordPress login Brute force / Web App Attack on client site.
2019-11-10 13:11:54
203.91.114.6 attack
Nov 10 06:16:35 dedicated sshd[30592]: Invalid user ina from 203.91.114.6 port 58932
2019-11-10 13:20:25
103.35.64.73 attackspam
2019-11-10T00:42:19.991262abusebot-7.cloudsearch.cf sshd\[9045\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.35.64.73  user=root
2019-11-10 09:32:28
183.87.134.98 attackbots
leo_www
2019-11-10 09:28:56

Recently Reported IPs

104.22.13.95 104.22.14.121 104.22.13.96 104.22.13.98
104.22.14.126 104.22.14.135 104.22.14.127 104.22.14.14
104.22.14.150 104.22.14.153 104.22.14.15 104.22.14.144
104.22.14.154 104.22.14.156 104.22.14.137 104.22.14.138
104.22.14.158 104.22.14.160 104.22.14.164 104.22.14.161