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

;; QUESTION SECTION:
;104.18.6.6.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 05:20:46 CST 2022
;; MSG SIZE  rcvd: 103
Host info
Host 6.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 6.6.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.42.7 attackbotsspam
23.02.2020 05:18:56 SSH access blocked by firewall
2020-02-23 13:20:25
203.202.240.189 attackbots
Unauthorized connection attempt detected from IP address 203.202.240.189 to port 1433 [J]
2020-02-23 13:43:38
103.36.125.225 attackspam
02/23/2020-05:58:14.739374 103.36.125.225 Protocol: 6 ET POLICY Cleartext WordPress Login
2020-02-23 13:18:46
101.108.217.85 attackspam
20/2/22@23:57:46: FAIL: Alarm-Network address from=101.108.217.85
20/2/22@23:57:46: FAIL: Alarm-Network address from=101.108.217.85
...
2020-02-23 13:35:20
52.34.83.11 attackspambots
02/23/2020-06:29:06.974297 52.34.83.11 Protocol: 6 SURICATA TLS invalid record/traffic
2020-02-23 13:39:17
222.186.175.183 attack
Feb 23 09:57:39 gw1 sshd[1792]: Failed password for root from 222.186.175.183 port 10296 ssh2
Feb 23 09:57:42 gw1 sshd[1792]: Failed password for root from 222.186.175.183 port 10296 ssh2
...
2020-02-23 13:35:54
94.209.140.142 attackbots
Unauthorized connection attempt detected from IP address 94.209.140.142 to port 2220 [J]
2020-02-23 13:31:56
49.213.163.213 attackspambots
Unauthorized connection attempt detected from IP address 49.213.163.213 to port 23 [J]
2020-02-23 13:26:04
185.195.27.206 attack
Feb 23 05:53:18 silence02 sshd[948]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.195.27.206
Feb 23 05:53:21 silence02 sshd[948]: Failed password for invalid user lucia from 185.195.27.206 port 33148 ssh2
Feb 23 05:57:34 silence02 sshd[1289]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.195.27.206
2020-02-23 13:40:59
177.67.4.95 attackspam
Automatic report - Port Scan Attack
2020-02-23 13:41:25
222.186.30.209 attackbotsspam
Feb 23 06:33:25 MK-Soft-Root2 sshd[21082]: Failed password for root from 222.186.30.209 port 41461 ssh2
Feb 23 06:33:28 MK-Soft-Root2 sshd[21082]: Failed password for root from 222.186.30.209 port 41461 ssh2
...
2020-02-23 13:43:18
91.221.124.62 attack
Feb 22 19:21:58 php1 sshd\[26365\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.221.124.62  user=root
Feb 22 19:22:00 php1 sshd\[26365\]: Failed password for root from 91.221.124.62 port 35182 ssh2
Feb 22 19:25:43 php1 sshd\[26674\]: Invalid user temp from 91.221.124.62
Feb 22 19:25:43 php1 sshd\[26674\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.221.124.62
Feb 22 19:25:45 php1 sshd\[26674\]: Failed password for invalid user temp from 91.221.124.62 port 37262 ssh2
2020-02-23 13:29:11
179.124.36.196 attack
Unauthorized connection attempt detected from IP address 179.124.36.196 to port 2220 [J]
2020-02-23 13:23:29
185.234.216.198 attack
Unauthorized connection attempt detected from IP address 185.234.216.198 to port 80 [J]
2020-02-23 13:36:26
2001:b011:700a:3f36:11:32ff:fe17:709d attackspam
Feb 23 05:57:55 wordpress wordpress(www.ruhnke.cloud)[51825]: XML-RPC authentication attempt for unknown user [login] from 2001:b011:700a:3f36:11:32ff:fe17:709d
2020-02-23 13:30:37

Recently Reported IPs

104.18.4.3 104.18.7.123 104.18.7.155 104.18.7.165
104.18.7.163 104.18.7.45 104.18.7.6 104.18.75.18
104.18.77.239 104.18.78.16 104.18.75.33 104.18.78.2
104.18.76.18 104.18.74.33 104.18.78.239 104.18.78.42
104.18.79.107 104.18.8.166 104.18.8.244 104.18.79.42