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

;; QUESTION SECTION:
;104.18.241.5.			IN	A

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

;; Query time: 27 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 14:52:36 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 5.241.18.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 5.241.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
192.144.171.165 attackbotsspam
web-1 [ssh] SSH Attack
2020-04-21 17:35:21
180.76.246.38 attack
Invalid user postgres from 180.76.246.38 port 40782
2020-04-21 17:54:41
117.6.133.235 attackbots
trying to access non-authorized port
2020-04-21 17:42:27
5.75.65.218 attack
trying to access non-authorized port
2020-04-21 18:11:35
113.160.96.110 attack
20/4/21@00:15:46: FAIL: Alarm-Network address from=113.160.96.110
...
2020-04-21 17:56:49
188.16.147.225 attackbots
Port probing on unauthorized port 23
2020-04-21 17:36:08
113.160.171.63 attackspam
Automatic report - Port Scan Attack
2020-04-21 17:49:33
31.44.247.180 attack
2020-04-21T06:31:01.752507abusebot-7.cloudsearch.cf sshd[2064]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.44.247.180  user=root
2020-04-21T06:31:04.403900abusebot-7.cloudsearch.cf sshd[2064]: Failed password for root from 31.44.247.180 port 33166 ssh2
2020-04-21T06:36:36.231539abusebot-7.cloudsearch.cf sshd[2349]: Invalid user zr from 31.44.247.180 port 50114
2020-04-21T06:36:36.248025abusebot-7.cloudsearch.cf sshd[2349]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.44.247.180
2020-04-21T06:36:36.231539abusebot-7.cloudsearch.cf sshd[2349]: Invalid user zr from 31.44.247.180 port 50114
2020-04-21T06:36:38.553398abusebot-7.cloudsearch.cf sshd[2349]: Failed password for invalid user zr from 31.44.247.180 port 50114 ssh2
2020-04-21T06:40:58.179198abusebot-7.cloudsearch.cf sshd[2674]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.44.247.180  user=root
2
...
2020-04-21 17:55:55
51.75.175.26 attackspam
WordPress login Brute force / Web App Attack on client site.
2020-04-21 17:40:22
185.234.219.23 attackbotsspam
Apr 21 11:30:38 ns3042688 courier-pop3d: LOGIN FAILED, user=test@keh-fix.com, ip=\[::ffff:185.234.219.23\]
...
2020-04-21 17:33:35
35.190.151.173 attack
Tried to login to my NAS device 272 times
2020-04-21 17:55:29
104.248.181.156 attackbots
Invalid user test from 104.248.181.156 port 38490
2020-04-21 18:01:27
140.213.13.111 attackbotsspam
Email rejected due to spam filtering
2020-04-21 17:51:59
217.170.206.138 attackbotsspam
firewall-block, port(s): 80/tcp
2020-04-21 17:58:34
222.186.15.10 attack
Unauthorized connection attempt detected from IP address 222.186.15.10 to port 22 [T]
2020-04-21 17:35:00

Recently Reported IPs

104.18.241.31 149.144.34.180 104.18.242.1 254.15.10.29
104.18.242.5 104.18.242.57 104.18.243.57 104.18.244.77
104.18.245.77 104.18.245.96 104.18.246.27 104.18.246.56
104.18.246.79 104.18.246.96 104.18.247.27 104.18.247.56
104.18.247.79 104.18.248.84 104.18.249.12 104.18.25.101