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

;; QUESTION SECTION:
;104.18.6.30.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 15:25:17 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 30.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 30.6.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
201.27.63.14 attack
Honeypot attack, port: 81, PTR: 201-27-63-14.dsl.telesp.net.br.
2020-02-08 18:14:35
154.123.132.11 attack
Honeypot attack, port: 5555, PTR: kiboko.telkom.co.ke.
2020-02-08 18:13:14
185.51.201.244 attack
IR_MNT-SHAHRAD_<177>1581137585 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2] {TCP} 185.51.201.244:43930
2020-02-08 17:54:31
91.121.179.189 attackspam
Port 11001 scan denied
2020-02-08 18:13:28
94.64.61.79 attackspam
Honeypot attack, port: 81, PTR: ppp-94-64-61-79.home.otenet.gr.
2020-02-08 17:53:54
93.157.158.220 attackbots
Honeypot attack, port: 5555, PTR: 93.157.158.220.hispeed.pl.
2020-02-08 18:11:22
49.235.169.15 attackspambots
Feb  8 06:13:34 firewall sshd[10517]: Invalid user new from 49.235.169.15
Feb  8 06:13:36 firewall sshd[10517]: Failed password for invalid user new from 49.235.169.15 port 60092 ssh2
Feb  8 06:18:31 firewall sshd[10713]: Invalid user ldm from 49.235.169.15
...
2020-02-08 17:50:56
104.248.187.165 attack
trying to access non-authorized port
2020-02-08 18:19:19
47.52.62.174 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-08 17:51:15
129.28.88.77 attackspam
sshd jail - ssh hack attempt
2020-02-08 17:43:56
221.2.35.78 attack
Feb  8 04:53:24 sshgateway sshd\[13023\]: Invalid user udo from 221.2.35.78
Feb  8 04:53:24 sshgateway sshd\[13023\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.2.35.78
Feb  8 04:53:27 sshgateway sshd\[13023\]: Failed password for invalid user udo from 221.2.35.78 port 7555 ssh2
2020-02-08 17:43:33
223.30.5.13 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-08 17:43:19
45.55.233.213 attackbots
Feb  8 05:52:31 ourumov-web sshd\[12071\]: Invalid user sbz from 45.55.233.213 port 35986
Feb  8 05:52:31 ourumov-web sshd\[12071\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.233.213
Feb  8 05:52:33 ourumov-web sshd\[12071\]: Failed password for invalid user sbz from 45.55.233.213 port 35986 ssh2
...
2020-02-08 18:19:50
140.143.33.202 attack
Feb  8 06:51:17 sd-53420 sshd\[22781\]: Invalid user qjz from 140.143.33.202
Feb  8 06:51:17 sd-53420 sshd\[22781\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.33.202
Feb  8 06:51:18 sd-53420 sshd\[22781\]: Failed password for invalid user qjz from 140.143.33.202 port 51888 ssh2
Feb  8 06:55:18 sd-53420 sshd\[23122\]: Invalid user hbw from 140.143.33.202
Feb  8 06:55:18 sd-53420 sshd\[23122\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.33.202
...
2020-02-08 18:20:55
85.105.133.168 attack
Automatic report - Port Scan Attack
2020-02-08 18:11:42

Recently Reported IPs

104.18.6.251 147.40.24.199 104.18.6.37 104.18.6.43
86.72.254.94 104.18.6.58 104.18.6.62 104.18.6.64
104.18.6.67 56.146.198.248 104.18.6.74 104.18.6.84
104.18.6.85 104.18.6.86 104.18.6.93 104.18.6.94
180.165.208.191 104.18.6.99 104.18.64.11 104.18.64.184