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

;; QUESTION SECTION:
;104.18.6.14.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 18:12:26 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 14.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 14.6.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.253.27.226 attackspambots
WordPress XMLRPC scan :: 222.253.27.226 2.016 - [08/Sep/2020:18:20:38  0000] [censored_1] "POST /xmlrpc.php HTTP/1.1" 503 18231 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2020-09-09 04:48:40
185.176.27.102 attackbots
Port scan: Attack repeated for 24 hours
2020-09-09 04:33:10
62.234.82.231 attackspam
Unauthorised connection attempt detected at AUO NODE 4. System is sshd. Protected by AUO Stack Web Application Firewall (WAF)
2020-09-09 04:50:13
154.0.170.4 attackspambots
Automatic report - Banned IP Access
2020-09-09 04:46:28
66.70.157.67 attack
Coordinated SSH brute-force attack from different IPs. pam_unix(sshd:auth):
2020-09-09 04:36:56
159.65.65.54 attack
Coordinated SSH brute-force attack from different IPs. pam_unix(sshd:auth):
2020-09-09 04:43:00
83.239.38.2 attack
Sep  8 19:34:45 lnxmail61 sshd[29659]: Failed password for root from 83.239.38.2 port 32796 ssh2
Sep  8 19:34:45 lnxmail61 sshd[29659]: Failed password for root from 83.239.38.2 port 32796 ssh2
2020-09-09 05:03:14
103.151.122.3 attackspam
mail auth brute force
2020-09-09 04:53:56
139.217.102.177 attack
Coordinated SSH brute-force attack from different IPs. pam_unix(sshd:auth):
2020-09-09 04:42:10
103.43.185.166 attackbotsspam
$f2bV_matches
2020-09-09 05:00:59
103.30.151.17 attackspambots
Coordinated SSH brute-force attack from different IPs. pam_unix(sshd:auth): user=root
2020-09-09 04:43:30
222.186.10.49 attack
Coordinated SSH brute-force attack from different IPs. pam_unix(sshd:auth):
2020-09-09 04:32:14
61.177.172.177 attackbots
$f2bV_matches
2020-09-09 04:37:31
106.13.82.231 attackspambots
Sep  8 18:41:32 ns382633 sshd\[11941\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.82.231  user=root
Sep  8 18:41:35 ns382633 sshd\[11941\]: Failed password for root from 106.13.82.231 port 41728 ssh2
Sep  8 18:53:48 ns382633 sshd\[13791\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.82.231  user=root
Sep  8 18:53:50 ns382633 sshd\[13791\]: Failed password for root from 106.13.82.231 port 38410 ssh2
Sep  8 18:57:14 ns382633 sshd\[14529\]: Invalid user speech-dispatcher from 106.13.82.231 port 50944
Sep  8 18:57:14 ns382633 sshd\[14529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.82.231
2020-09-09 05:08:10
45.142.120.137 attackbotsspam
2020-09-08T22:51:54.227750www postfix/smtpd[12134]: warning: unknown[45.142.120.137]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-09-08T22:52:34.339090www postfix/smtpd[12389]: warning: unknown[45.142.120.137]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-09-08T22:53:13.069534www postfix/smtpd[12134]: warning: unknown[45.142.120.137]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-09-09 05:01:22

Recently Reported IPs

104.18.6.137 104.18.6.140 104.18.6.148 104.18.6.168
104.18.6.169 104.18.6.172 104.18.6.177 104.18.6.178
104.18.6.18 104.18.6.187 104.18.6.198 104.18.6.199
104.18.6.2 104.18.6.211 104.18.6.213 104.18.6.236
104.18.6.244 104.18.6.248 104.18.6.3 104.18.6.34