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

;; QUESTION SECTION:
;159.104.147.147.		IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jul 23 06:34:16 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 147.147.104.159.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.147.104.159.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
74.208.148.227 attackbotsspam
Spam Timestamp : 09-Nov-19 15:35   BlockList Provider  combined abuse   (861)
2019-11-10 06:40:14
109.167.249.41 attackspam
postfix
2019-11-10 06:14:34
189.212.91.254 attack
Automatic report - Port Scan Attack
2019-11-10 06:26:09
87.101.39.214 attackbots
Nov  9 16:54:03 localhost sshd\[45325\]: Invalid user nasshare from 87.101.39.214 port 37206
Nov  9 16:54:03 localhost sshd\[45325\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.101.39.214
Nov  9 16:54:04 localhost sshd\[45325\]: Failed password for invalid user nasshare from 87.101.39.214 port 37206 ssh2
Nov  9 16:57:57 localhost sshd\[45405\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.101.39.214  user=root
Nov  9 16:57:58 localhost sshd\[45405\]: Failed password for root from 87.101.39.214 port 55284 ssh2
...
2019-11-10 06:37:10
36.155.10.19 attackspam
$f2bV_matches_ltvn
2019-11-10 06:49:04
80.211.35.16 attackspam
Nov  9 18:25:15 sauna sshd[88792]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.35.16
Nov  9 18:25:17 sauna sshd[88792]: Failed password for invalid user ulcer from 80.211.35.16 port 48932 ssh2
...
2019-11-10 06:17:13
203.153.113.226 attackbots
Autoban   203.153.113.226 AUTH/CONNECT
2019-11-10 06:16:38
192.241.210.224 attackspambots
5x Failed Password
2019-11-10 06:19:19
5.196.7.123 attackspam
Nov  9 17:47:06 SilenceServices sshd[2387]: Failed password for root from 5.196.7.123 port 39090 ssh2
Nov  9 17:50:59 SilenceServices sshd[5406]: Failed password for root from 5.196.7.123 port 47478 ssh2
2019-11-10 06:45:33
222.74.73.202 attackbots
Spam emails were sent from this SMTP server. 
Some of this kind of spam emails attempted to camouflage the SMTP servers with 27.85.176.228 (a KDDI's legitimate server). 
The URLs in the spam messages were such as : 
- http :// ds85e6a.xyz/asint/ura-ac02/prof.php?pid=1 (61.14.210.110)
- http :// ds85e6a.xyz/asint/stop/
The spammer used the following domains for the email addresses in the sites.:
- mlstp.0ch.biz (The domain "0ch.biz" used "ns01.kix.ad.jp" and "ns02" for the name servers. Its registrant was "MEDIAWARS CO.,Ltd.". Its registrar was "IDC Frontier Inc.".)
- lover-amazing.com (Its registrar was "GMO Internet, Inc.".)
2019-11-10 06:22:21
91.142.238.237 attack
Chat Spam
2019-11-10 06:20:15
142.44.137.62 attack
Nov  9 17:53:31 legacy sshd[23274]: Failed password for root from 142.44.137.62 port 60290 ssh2
Nov  9 17:57:17 legacy sshd[23381]: Failed password for root from 142.44.137.62 port 41384 ssh2
Nov  9 18:00:57 legacy sshd[23523]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.137.62
...
2019-11-10 06:23:41
134.175.229.28 attackspambots
Nov  5 05:27:57 h2040555 sshd[15646]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.229.28  user=r.r
Nov  5 05:27:59 h2040555 sshd[15646]: Failed password for r.r from 134.175.229.28 port 53468 ssh2
Nov  5 05:27:59 h2040555 sshd[15646]: Received disconnect from 134.175.229.28: 11: Bye Bye [preauth]
Nov  5 05:50:23 h2040555 sshd[15903]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.229.28  user=r.r
Nov  5 05:50:25 h2040555 sshd[15903]: Failed password for r.r from 134.175.229.28 port 59350 ssh2
Nov  5 05:50:25 h2040555 sshd[15903]: Received disconnect from 134.175.229.28: 11: Bye Bye [preauth]
Nov  5 05:55:06 h2040555 sshd[15947]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.229.28  user=r.r
Nov  5 05:55:08 h2040555 sshd[15947]: Failed password for r.r from 134.175.229.28 port 39506 ssh2
Nov  5 05:55:09 h2040555 sshd[15947........
-------------------------------
2019-11-10 06:12:57
171.244.21.204 attackspam
Spam Timestamp : 09-Nov-19 15:08   BlockList Provider  combined abuse   (856)
2019-11-10 06:46:28
68.183.160.63 attackbotsspam
2019-11-09T22:42:29.968109hz01.yumiweb.com sshd\[24130\]: Invalid user service from 68.183.160.63 port 53058
2019-11-09T22:45:01.541690hz01.yumiweb.com sshd\[24132\]: Invalid user service from 68.183.160.63 port 39020
2019-11-09T22:47:32.014672hz01.yumiweb.com sshd\[24140\]: Invalid user service from 68.183.160.63 port 53248
...
2019-11-10 06:32:01

Recently Reported IPs

159.102.239.64 159.102.80.149 159.100.96.88 159.102.183.214
159.102.53.59 159.100.63.103 159.102.86.162 159.103.248.8
159.100.34.122 159.102.221.176 159.101.207.77 159.102.228.137
159.101.160.11 159.100.64.107 159.102.69.139 159.102.91.148
159.103.156.41 159.102.188.101 159.101.48.1 159.100.235.79