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.12.94 spambotsattackproxynormal
Ip
2022-05-11 11:40:42
104.18.116.17 attack
14red.com casino spam - casino with very bad reputation
Received: from HE1EUR01HT170.eop-EUR01.prod.protection.outlook.com (2603:10a6:802:1::35) by VI1PR0501MB2301.eurprd05.prod.outlook.com with HTTPS via VI1PR0902CA0046.EURPRD09.PROD.OUTLOOK.COM; Wed, 31 Jul 2019 16:52:30 +0000 Received: from HE1EUR01FT007.eop-EUR01.prod.protection.outlook.com (10.152.0.51) by HE1EUR01HT170.eop-EUR01.prod.protection.outlook.com (10.152.1.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.14; Wed, 31 Jul 2019 16:52:30 +0000 Authentication-Results: spf=none (sender IP is 169.159.171.139) smtp.mailfrom=luxido.cz; hotmail.co.uk; dkim=none (message not signed) header.d=none;hotmail.co.uk; dmarc=none action=none header.from=luxido.cz; Received-SPF: None (protection.outlook.com: luxido.cz does not designate permitted sender hosts) Received: from static-public-169.159.171.igen.co.za (169.159.171.139)
2019-08-01 05:33:34
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.18.1.228
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19296
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.18.1.228.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 05:13:10 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 228.1.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 228.1.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
186.32.195.194 attackbots
detected by Fail2Ban
2020-06-10 03:36:42
72.220.8.139 attackspam
Jun  9 17:31:33 web2 sshd[23023]: Failed password for root from 72.220.8.139 port 54181 ssh2
2020-06-10 03:40:10
49.73.235.149 attackbotsspam
Jun  9 15:45:30 ns381471 sshd[2781]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.73.235.149
Jun  9 15:45:31 ns381471 sshd[2781]: Failed password for invalid user wow from 49.73.235.149 port 49485 ssh2
2020-06-10 03:58:59
129.204.235.54 attackbotsspam
Jun  9 21:31:23 hosting sshd[28535]: Invalid user martin from 129.204.235.54 port 59144
...
2020-06-10 03:31:01
58.67.221.184 attack
(sshd) Failed SSH login from 58.67.221.184 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun  9 17:37:28 s1 sshd[7375]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.67.221.184  user=root
Jun  9 17:37:29 s1 sshd[7375]: Failed password for root from 58.67.221.184 port 37690 ssh2
Jun  9 17:39:44 s1 sshd[7401]: Invalid user shhan from 58.67.221.184 port 59270
Jun  9 17:39:46 s1 sshd[7401]: Failed password for invalid user shhan from 58.67.221.184 port 59270 ssh2
Jun  9 17:41:33 s1 sshd[7448]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.67.221.184  user=root
2020-06-10 03:34:49
34.106.230.78 attack
34.106.230.78 - - \[09/Jun/2020:11:04:39 -0700\] "GET /wp-login.php HTTP/1.1" 301 561 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"34.106.230.78 - - \[09/Jun/2020:11:04:39 -0700\] "GET /wp-login.php HTTP/1.1" 404 11555 "http://stitch-maps.com/wp-login.php" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
...
2020-06-10 03:45:42
117.240.165.32 attackbotsspam
Unauthorized connection attempt from IP address 117.240.165.32 on Port 445(SMB)
2020-06-10 03:57:38
185.232.30.130 attack
Unauthorized connection attempt from IP address 185.232.30.130 on Port 3389(RDP)
2020-06-10 03:38:50
182.23.68.119 attackbots
Fail2Ban Ban Triggered
2020-06-10 04:01:00
113.99.127.190 attackspambots
bruteforce detected
2020-06-10 04:09:08
167.99.101.199 attack
C2,WP GET /wp-login.php
2020-06-10 04:01:27
139.167.49.171 attackspam
RDP Bruteforce
2020-06-10 03:43:01
119.44.20.30 attackspam
Jun  9 20:10:36 webhost01 sshd[18457]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.44.20.30
Jun  9 20:10:38 webhost01 sshd[18457]: Failed password for invalid user yaoyiming from 119.44.20.30 port 17966 ssh2
...
2020-06-10 03:44:25
218.17.185.31 attackspam
Jun  9 15:01:56 * sshd[32204]: Failed password for root from 218.17.185.31 port 39626 ssh2
Jun  9 15:02:50 * sshd[32313]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.17.185.31
2020-06-10 03:58:08
37.49.226.157 attackspam
(sshd) Failed SSH login from 37.49.226.157 (NL/Netherlands/-): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun  9 21:15:09 ubnt-55d23 sshd[513]: Did not receive identification string from 37.49.226.157 port 48382
Jun  9 21:15:16 ubnt-55d23 sshd[514]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.49.226.157  user=root
2020-06-10 03:33:35

Recently Reported IPs

104.18.1.2 104.18.1.237 104.18.1.45 104.18.1.50
104.18.1.76 104.18.1.82 104.18.1.93 104.18.10.10
104.18.10.11 104.18.10.115 104.18.10.149 104.18.10.177
104.18.10.178 104.18.10.183 104.18.10.188 104.18.10.212
104.18.10.234 104.18.10.249 104.18.10.5 104.18.10.63