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

;; QUESTION SECTION:
;104.44.63.142.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 01:40:50 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 142.63.44.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 142.63.44.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
41.237.166.106 attackbots
Attempt to attack host OS, exploiting network vulnerabilities, on 10-01-2020 04:50:11.
2020-01-10 18:20:31
91.192.168.247 attackbotsspam
<6 unauthorized SSH connections
2020-01-10 18:41:45
45.168.35.229 attackspambots
v+ssh-bruteforce
2020-01-10 18:42:38
184.105.139.97 attack
2 Attack(s) Detected
[DoS Attack: TCP/UDP Chargen] from source: 184.105.139.97, port 45034, Thursday, January 09, 2020 00:09:34 
[DoS Attack: TCP/UDP Chargen] from source: 184.105.139.97, port 38333, Thursday, January 02, 2020 23:07:34
2020-01-10 18:35:55
94.102.53.10 attack
Jan 10 10:50:40 tuxlinux kernel: [UFW BLOCK] IN=ens192 OUT= MAC=00:50:56:bc:13:b8:30:e4:db:97:3e:3f:08:00 SRC=94.102.53.10 DST=217.198.117.163 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=63968 PROTO=TCP SPT=53782 DPT=27521 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2020-01-10 18:19:55
184.105.247.226 attack
firewall-block, port(s): 27017/tcp
2020-01-10 18:35:15
190.147.159.34 attackspam
Jan 10 05:46:10 legacy sshd[22990]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.147.159.34
Jan 10 05:46:13 legacy sshd[22990]: Failed password for invalid user db from 190.147.159.34 port 39601 ssh2
Jan 10 05:50:02 legacy sshd[23239]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.147.159.34
...
2020-01-10 18:27:32
117.247.180.249 attackbots
1578631829 - 01/10/2020 05:50:29 Host: 117.247.180.249/117.247.180.249 Port: 445 TCP Blocked
2020-01-10 18:13:19
49.51.34.136 attackspambots
17988/tcp 2030/tcp 7170/tcp...
[2019-11-28/2020-01-10]10pkt,10pt.(tcp)
2020-01-10 18:40:36
92.118.160.49 attackspam
port scan and connect, tcp 990 (ftps)
2020-01-10 18:53:28
222.186.30.57 attack
SSH Brute Force, server-1 sshd[6100]: Failed password for root from 222.186.30.57 port 28371 ssh2
2020-01-10 18:23:37
58.21.173.126 attack
firewall-block, port(s): 8090/tcp
2020-01-10 18:29:50
190.236.203.18 attackspam
Jan 10 05:50:01 grey postfix/smtpd\[32661\]: NOQUEUE: reject: RCPT from unknown\[190.236.203.18\]: 554 5.7.1 Service unavailable\; Client host \[190.236.203.18\] blocked using bl.spamcop.net\; Blocked - see https://www.spamcop.net/bl.shtml\?190.236.203.18\; from=\ to=\ proto=ESMTP helo=\<\[190.236.203.18\]\>
...
2020-01-10 18:30:21
123.25.85.155 attackspam
Attempt to attack host OS, exploiting network vulnerabilities, on 10-01-2020 04:50:09.
2020-01-10 18:22:01
87.106.202.9 attackspam
firewall-block, port(s): 64190/tcp
2020-01-10 18:29:32

Recently Reported IPs

216.105.7.113 97.152.128.239 131.24.2.209 197.251.197.144
246.190.173.157 37.3.225.103 79.228.44.55 175.1.241.72
156.214.154.57 53.147.67.216 58.109.225.247 52.147.158.32
186.137.248.24 141.70.224.143 225.196.62.125 153.254.140.214
64.21.60.138 38.112.95.2 48.134.199.248 163.81.45.27