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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;242.47.94.104.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 13:17:27 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 104.94.47.242.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 104.94.47.242.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
201.217.194.29 attackbotsspam
Automatic report - Banned IP Access
2019-07-28 14:12:55
148.72.207.232 attackbots
2019-07-28T05:18:57.843967abusebot.cloudsearch.cf sshd\[18768\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-148-72-207-232.ip.secureserver.net  user=root
2019-07-28 13:53:32
180.76.119.77 attack
2019-07-28T01:10:38.387126abusebot-8.cloudsearch.cf sshd\[27200\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.119.77  user=root
2019-07-28 13:26:24
134.209.161.167 attackbots
2019-07-28T06:16:27.496970abusebot-8.cloudsearch.cf sshd\[28457\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.161.167  user=root
2019-07-28 14:29:07
197.248.38.174 attack
firewall-block, port(s): 445/tcp
2019-07-28 13:54:42
220.231.216.115 attackbotsspam
Port scan and direct access per IP instead of hostname
2019-07-28 14:32:35
180.76.232.160 attackbots
Jul 28 02:58:45 mail sshd\[27448\]: Invalid user summer12 from 180.76.232.160 port 49024
Jul 28 02:58:45 mail sshd\[27448\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.232.160
Jul 28 02:58:47 mail sshd\[27448\]: Failed password for invalid user summer12 from 180.76.232.160 port 49024 ssh2
Jul 28 03:00:56 mail sshd\[28315\]: Invalid user ntl from 180.76.232.160 port 39454
Jul 28 03:00:56 mail sshd\[28315\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.232.160
2019-07-28 13:30:01
203.205.35.211 attackspambots
Port scan and direct access per IP instead of hostname
2019-07-28 14:38:00
203.188.244.123 attack
Port scan and direct access per IP instead of hostname
2019-07-28 14:39:03
187.85.212.57 attackspam
Distributed brute force attack
2019-07-28 13:17:16
94.240.48.38 attack
2019-07-28T06:50:39.575340lon01.zurich-datacenter.net sshd\[26254\]: Invalid user sa6 from 94.240.48.38 port 58446
2019-07-28T06:50:39.582704lon01.zurich-datacenter.net sshd\[26254\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=cloud.zmlukow.pl
2019-07-28T06:50:41.850793lon01.zurich-datacenter.net sshd\[26254\]: Failed password for invalid user sa6 from 94.240.48.38 port 58446 ssh2
2019-07-28T06:55:07.960017lon01.zurich-datacenter.net sshd\[26335\]: Invalid user P@ssw0rd0 from 94.240.48.38 port 54426
2019-07-28T06:55:07.967847lon01.zurich-datacenter.net sshd\[26335\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=cloud.zmlukow.pl
...
2019-07-28 13:38:09
195.154.179.24 attackbots
\[2019-07-28 06:18:43\] SECURITY\[1715\] res_security_log.c: SecurityEvent="InvalidAccountID",EventTV="2019-07-28T06:18:43.999+0200",Severity="Error",Service="PJSIP",EventVersion="1",AccountID="7716",SessionID="1999824501-591460506-1380669656",LocalAddress="IPV4/UDP/188.40.118.248/5060",RemoteAddress="IPV4/UDP/195.154.179.24/63142"
\[2019-07-28 06:18:47\] SECURITY\[1715\] res_security_log.c: SecurityEvent="InvalidAccountID",EventTV="2019-07-28T06:18:47.516+0200",Severity="Error",Service="PJSIP",EventVersion="1",AccountID="adrianne",SessionID="779023-1389991565-479645300",LocalAddress="IPV4/UDP/188.40.118.248/5060",RemoteAddress="IPV4/UDP/195.154.179.24/52579"
\[2019-07-28 06:18:51\] SECURITY\[1715\] res_security_log.c: SecurityEvent="InvalidAccountID",EventTV="2019-07-28T06:18:51.100+0200",Severity="Error",Service="PJSIP",EventVersion="1",AccountID="tamisha",SessionID="1739035404-361686877-1498047484",LocalAddress="IPV4/UDP/188.40.118.248/5060",RemoteAddress="IPV4/UDP/195.154.179.24/58610"
\[2019-07-28 06:18
2019-07-28 13:28:24
107.170.197.82 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-07-28 14:02:36
23.225.121.194 attackspam
Port scan and direct access per IP instead of hostname
2019-07-28 14:28:29
71.6.167.142 attack
28.07.2019 05:06:22 Connection to port 2455 blocked by firewall
2019-07-28 13:42:10

Recently Reported IPs

153.9.144.44 71.128.125.32 209.231.125.139 9.96.114.104
227.107.121.250 94.35.97.148 80.204.94.210 69.87.198.4
163.194.37.204 187.13.179.196 209.102.220.4 150.179.225.186
198.73.99.23 182.109.155.21 184.227.65.35 144.87.100.158
36.62.96.155 197.107.160.178 247.221.250.79 234.100.212.59