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

;; QUESTION SECTION:
;104.22.46.147.			IN	A

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

;; Query time: 120 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:36:06 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 147.46.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 147.46.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
118.69.70.222 attack
Unauthorized connection attempt from IP address 118.69.70.222 on Port 445(SMB)
2019-10-02 08:08:13
41.214.51.2 attackspambots
Unauthorized connection attempt from IP address 41.214.51.2 on Port 445(SMB)
2019-10-02 08:07:34
220.92.16.90 attackspam
Triggered by Fail2Ban at Vostok web server
2019-10-02 08:12:26
209.97.169.136 attack
2019-10-01T23:44:29.749489shield sshd\[12352\]: Invalid user fen from 209.97.169.136 port 55728
2019-10-01T23:44:29.753974shield sshd\[12352\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.97.169.136
2019-10-01T23:44:32.339080shield sshd\[12352\]: Failed password for invalid user fen from 209.97.169.136 port 55728 ssh2
2019-10-01T23:48:58.681691shield sshd\[13352\]: Invalid user teamspeak3 from 209.97.169.136 port 40802
2019-10-01T23:48:58.686197shield sshd\[13352\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.97.169.136
2019-10-02 07:51:29
117.194.80.156 attackspam
Unauthorized connection attempt from IP address 117.194.80.156 on Port 445(SMB)
2019-10-02 08:13:18
167.99.65.138 attackspam
Oct  1 13:40:26 sachi sshd\[28177\]: Invalid user admin from 167.99.65.138
Oct  1 13:40:26 sachi sshd\[28177\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
Oct  1 13:40:27 sachi sshd\[28177\]: Failed password for invalid user admin from 167.99.65.138 port 46100 ssh2
Oct  1 13:45:04 sachi sshd\[28626\]: Invalid user ftptest from 167.99.65.138
Oct  1 13:45:04 sachi sshd\[28626\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
2019-10-02 08:29:35
64.202.187.152 attack
Jul 22 18:48:11 vtv3 sshd\[18934\]: Invalid user dv from 64.202.187.152 port 43614
Jul 22 18:48:11 vtv3 sshd\[18934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.152
Jul 22 18:48:13 vtv3 sshd\[18934\]: Failed password for invalid user dv from 64.202.187.152 port 43614 ssh2
Jul 22 18:52:38 vtv3 sshd\[21139\]: Invalid user testuser from 64.202.187.152 port 40446
Jul 22 18:52:38 vtv3 sshd\[21139\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.152
Jul 22 19:05:40 vtv3 sshd\[28165\]: Invalid user jira from 64.202.187.152 port 59174
Jul 22 19:05:40 vtv3 sshd\[28165\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.152
Jul 22 19:05:42 vtv3 sshd\[28165\]: Failed password for invalid user jira from 64.202.187.152 port 59174 ssh2
Jul 22 19:10:07 vtv3 sshd\[30382\]: Invalid user andi from 64.202.187.152 port 56010
Jul 22 19:10:07 vtv3 sshd\[30382\]: pa
2019-10-02 08:20:30
89.248.172.85 attack
Port scan attempt detected by AWS-CCS, CTS, India
2019-10-02 08:23:01
190.36.45.226 attack
Unauthorized connection attempt from IP address 190.36.45.226 on Port 445(SMB)
2019-10-02 07:55:37
120.14.161.58 attack
Unauthorised access (Oct  2) SRC=120.14.161.58 LEN=40 TTL=49 ID=60423 TCP DPT=8080 WINDOW=39603 SYN
2019-10-02 08:34:44
203.110.179.26 attackspambots
Oct  2 01:04:20 ns41 sshd[13145]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.110.179.26
2019-10-02 07:53:47
212.156.99.114 attackbots
Unauthorized connection attempt from IP address 212.156.99.114 on Port 445(SMB)
2019-10-02 07:58:48
91.108.64.2 attackbotsspam
Oct  2 04:01:54 webhost01 sshd[31017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.108.64.2
Oct  2 04:01:56 webhost01 sshd[31017]: Failed password for invalid user ngit from 91.108.64.2 port 51040 ssh2
...
2019-10-02 08:19:12
118.163.149.163 attack
Oct  2 01:10:48 MK-Soft-VM6 sshd[14829]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.163.149.163 
Oct  2 01:10:50 MK-Soft-VM6 sshd[14829]: Failed password for invalid user aos from 118.163.149.163 port 36280 ssh2
...
2019-10-02 07:56:00
140.143.170.123 attack
Oct  2 01:54:37 OPSO sshd\[18053\]: Invalid user gustav from 140.143.170.123 port 43392
Oct  2 01:54:37 OPSO sshd\[18053\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.170.123
Oct  2 01:54:40 OPSO sshd\[18053\]: Failed password for invalid user gustav from 140.143.170.123 port 43392 ssh2
Oct  2 01:59:26 OPSO sshd\[19387\]: Invalid user zenon from 140.143.170.123 port 52626
Oct  2 01:59:26 OPSO sshd\[19387\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.170.123
2019-10-02 08:05:43

Recently Reported IPs

104.22.46.139 104.22.46.132 104.22.46.145 104.22.46.168
104.22.46.148 104.22.46.170 104.22.46.188 104.22.46.200
104.22.46.199 104.22.46.214 104.22.46.193 104.22.46.225
104.22.46.201 104.22.46.190 104.22.46.226 104.22.46.183
104.22.46.218 104.22.46.232 104.22.46.229 104.22.46.238