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:
IP Type Details Datetime
104.18.68.149 attackbots
"MarketingPromoSystems, 8 The Green Suite #5828 Dover DE" 185.230.46.95 - phishing redirect www1.innovationaltech.xyz
2020-05-24 23:39:23
104.18.69.149 attackspam
"MarketingPromoSystems, 8 The Green Suite #5828 Dover DE" 185.230.46.95 - phishing redirect www1.innovationaltech.xyz
2020-05-24 23:05:53
104.18.69.106 attackbots
#BLOCKED Misbehaving Domain (Bad Bots Host) ##TrustME
2020-02-25 20:43:16
104.18.69.106 attack
siteaudit.crawler.semrush.com - - \[27/Oct/2019:04:48:48 +0100\] "GET /robots.txt HTTP/1.1" 200 4578 "-" "Mozilla/5.0 \(compatible\; Googlebot/2.1\; +http://www.google.com/bot.html\)"
siteaudit.crawler.semrush.com - - \[27/Oct/2019:04:48:49 +0100\] "GET /galerie/villa-bunterkund.html HTTP/1.1" 200 10713 "-" "Mozilla/5.0 \(compatible\; Googlebot/2.1\; +http://www.google.com/bot.html\)"
siteaudit.crawler.semrush.com - - \[27/Oct/2019:04:48:55 +0100\] "GET / HTTP/1.1" 200 9534 "-" "Mozilla/5.0 \(compatible\; Googlebot/2.1\; +http://www.google.com/bot.html\)"
...
2019-10-27 17:26:46
104.18.62.38 attackbots
Enormous amount of pornographic dating spam emails. .roughly 80 Received today. I have had enough of this constant bilge flood. Stop these smut peddlers NOW!!
2019-08-25 07:51:10
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.18.6.41
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21774
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.18.6.41.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 01:54:45 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 41.6.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 41.6.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
196.203.31.154 attack
Tried sshing with brute force.
2019-07-19 19:45:10
45.81.0.105 attackbots
0,55-00/01 concatform PostRequest-Spammer scoring: paris
2019-07-19 19:46:46
165.22.244.146 attackspam
Jul 19 13:55:24 mail sshd\[17237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.244.146  user=root
Jul 19 13:55:26 mail sshd\[17237\]: Failed password for root from 165.22.244.146 port 41904 ssh2
Jul 19 14:00:43 mail sshd\[18675\]: Invalid user manager from 165.22.244.146 port 38848
Jul 19 14:00:43 mail sshd\[18675\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.244.146
Jul 19 14:00:44 mail sshd\[18675\]: Failed password for invalid user manager from 165.22.244.146 port 38848 ssh2
2019-07-19 20:04:53
121.127.12.6 attackspam
invalid login attempt
2019-07-19 20:05:40
51.38.133.58 attackbotsspam
Invalid user system from 51.38.133.58 port 54874
2019-07-19 20:11:12
218.25.89.90 attackbotsspam
Jul 19 08:04:09 debian sshd\[5947\]: Invalid user jim from 218.25.89.90 port 48096
Jul 19 08:04:09 debian sshd\[5947\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.25.89.90
Jul 19 08:04:11 debian sshd\[5947\]: Failed password for invalid user jim from 218.25.89.90 port 48096 ssh2
...
2019-07-19 20:07:35
207.180.241.54 attackbots
[DoS attack: ACK Scan] from source: 207.180.241.54
2019-07-19 20:03:45
59.25.197.134 attackbotsspam
$f2bV_matches
2019-07-19 19:53:47
114.44.130.219 attack
TCP port 445 (SMB) attempt blocked by firewall. [2019-07-19 07:50:22]
2019-07-19 20:30:31
46.105.244.17 attackspam
Jul 19 12:09:26 ArkNodeAT sshd\[5595\]: Invalid user np from 46.105.244.17
Jul 19 12:09:26 ArkNodeAT sshd\[5595\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.244.17
Jul 19 12:09:27 ArkNodeAT sshd\[5595\]: Failed password for invalid user np from 46.105.244.17 port 43260 ssh2
2019-07-19 19:52:01
2.44.166.236 attackbots
Automatic report - Port Scan Attack
2019-07-19 20:04:06
201.242.149.146 attack
TCP port 23 (Telnet) attempt blocked by firewall. [2019-07-19 07:50:22]
2019-07-19 20:30:00
132.247.16.76 attackspam
Jul 19 05:24:19 TORMINT sshd\[7787\]: Invalid user frank from 132.247.16.76
Jul 19 05:24:19 TORMINT sshd\[7787\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.247.16.76
Jul 19 05:24:21 TORMINT sshd\[7787\]: Failed password for invalid user frank from 132.247.16.76 port 44453 ssh2
...
2019-07-19 19:50:32
81.202.61.93 attackspambots
Invalid user user from 81.202.61.93 port 41400
2019-07-19 20:13:47
219.88.80.75 attackspam
WordPress XMLRPC scan :: 219.88.80.75 0.108 BYPASS [19/Jul/2019:20:53:32  1000] [censored_1] "GET /xmlrpc.php HTTP/1.1" 405 53 "-" "Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1"
2019-07-19 19:54:56

Recently Reported IPs

104.18.6.242 104.18.6.39 104.18.6.51 104.21.65.61
104.18.6.63 104.18.6.61 104.18.6.66 104.18.6.91
104.18.6.89 104.18.6.70 104.18.6.65 104.18.6.83
104.18.6.53 104.18.6.75 104.18.64.60 104.21.65.62
104.18.6.95 104.18.6.96 104.18.64.79 104.18.65.79