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

;; QUESTION SECTION:
;104.18.9.66.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 05:58:15 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 66.9.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 66.9.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
203.143.12.26 attackspam
2019-09-24 07:15:05,210 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 203.143.12.26
2019-09-24 07:48:34,909 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 203.143.12.26
2019-09-24 08:20:46,966 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 203.143.12.26
2019-09-24 08:52:35,851 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 203.143.12.26
2019-09-24 09:24:41,557 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 203.143.12.26
...
2019-09-24 19:40:05
37.98.114.228 attackspambots
2019-09-24T04:32:30.273739abusebot-6.cloudsearch.cf sshd\[3842\]: Invalid user admin from 37.98.114.228 port 57156
2019-09-24 18:22:15
91.121.110.97 attackbotsspam
Sep 24 13:17:34 core sshd[21117]: Invalid user rp from 91.121.110.97 port 55402
Sep 24 13:17:35 core sshd[21117]: Failed password for invalid user rp from 91.121.110.97 port 55402 ssh2
...
2019-09-24 19:34:09
103.28.52.13 attackbotsspam
MYH,DEF GET /wp-login.php
2019-09-24 19:16:36
217.11.48.148 attackbotsspam
SS1,DEF GET /wp-login.php
2019-09-24 19:22:59
173.45.164.2 attackbots
Sep 24 13:37:28 nextcloud sshd\[24893\]: Invalid user dieter from 173.45.164.2
Sep 24 13:37:28 nextcloud sshd\[24893\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.45.164.2
Sep 24 13:37:29 nextcloud sshd\[24893\]: Failed password for invalid user dieter from 173.45.164.2 port 55238 ssh2
...
2019-09-24 19:42:21
123.21.33.151 attack
fail2ban
2019-09-24 19:49:39
128.199.230.56 attackspambots
Sep 24 05:48:29 MK-Soft-Root2 sshd[10424]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.230.56 
Sep 24 05:48:32 MK-Soft-Root2 sshd[10424]: Failed password for invalid user krandasi from 128.199.230.56 port 56525 ssh2
...
2019-09-24 19:32:12
92.53.74.14 attackspam
Automatic report - Banned IP Access
2019-09-24 19:52:19
120.36.182.222 attackspambots
(ftpd) Failed FTP login from 120.36.182.222 (CN/China/222.182.36.120.broad.xm.fj.dynamic.163data.com.cn): 10 in the last 3600 secs
2019-09-24 19:37:43
80.237.199.97 attackspambots
$f2bV_matches
2019-09-24 19:21:21
177.92.60.116 attack
Sep 24 06:09:32 nandi sshd[3212]: reveeclipse mapping checking getaddrinfo for 116.60.92.177.dynamic.copel.net [177.92.60.116] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep 24 06:09:32 nandi sshd[3212]: Invalid user pi from 177.92.60.116
Sep 24 06:09:32 nandi sshd[3209]: reveeclipse mapping checking getaddrinfo for 116.60.92.177.dynamic.copel.net [177.92.60.116] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep 24 06:09:32 nandi sshd[3209]: Invalid user pi from 177.92.60.116
Sep 24 06:09:32 nandi sshd[3212]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.92.60.116 
Sep 24 06:09:32 nandi sshd[3209]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.92.60.116 
Sep 24 06:09:34 nandi sshd[3212]: Failed password for invalid user pi from 177.92.60.116 port 10650 ssh2
Sep 24 06:09:34 nandi sshd[3209]: Failed password for invalid user pi from 177.92.60.116 port 32996 ssh2
Sep 24 06:09:35 nandi sshd[3209]: Co........
-------------------------------
2019-09-24 19:57:56
115.238.249.100 attackbotsspam
Sep 24 01:34:45 ws22vmsma01 sshd[167662]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.238.249.100
Sep 24 01:34:47 ws22vmsma01 sshd[167662]: Failed password for invalid user samba from 115.238.249.100 port 31593 ssh2
...
2019-09-24 19:24:03
62.234.66.50 attackspam
Sep 24 13:39:31 saschabauer sshd[29750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.66.50
Sep 24 13:39:33 saschabauer sshd[29750]: Failed password for invalid user rootme from 62.234.66.50 port 56485 ssh2
2019-09-24 19:41:00
185.204.59.8 attackbots
2019-09-24T05:48:15.958176 X postfix/smtpd[59372]: NOQUEUE: reject: RCPT from unknown[185.204.59.8]: 554 5.7.1 Service unavailable; Client host [185.204.59.8] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/185.204.59.8 / https://www.spamhaus.org/sbl/query/SBLCSS; from= to= proto=ESMTP helo=
2019-09-24 19:45:09

Recently Reported IPs

104.18.9.65 104.18.9.91 104.18.9.94 104.18.9.99
104.18.90.198 104.18.90.237 104.18.90.25 104.18.91.198
104.18.92.198 104.18.92.28 104.18.92.72 104.18.93.198
104.18.93.28 104.18.94.198 104.18.94.91 165.109.242.43
104.18.96.26 104.18.96.65 104.18.97.12 104.18.97.26