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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.18.42.227
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54252
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.18.42.227.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 20 11:46:06 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 227.42.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 227.42.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
192.162.144.183 attack
Honeypot attack, port: 81, PTR: PTR record not found
2020-03-30 16:42:58
106.12.219.184 attackbotsspam
Mar 30 08:40:46 sso sshd[13861]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.219.184
Mar 30 08:40:48 sso sshd[13861]: Failed password for invalid user against from 106.12.219.184 port 59138 ssh2
...
2020-03-30 16:35:08
188.226.149.92 attack
<6 unauthorized SSH connections
2020-03-30 16:34:15
51.15.136.91 attackspambots
Mar 30 03:14:54 s158375 sshd[25238]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.136.91
2020-03-30 16:29:40
139.162.122.110 attack
SSH authentication failure x 6 reported by Fail2Ban
...
2020-03-30 16:33:20
196.44.191.3 attack
Brute-force attempt banned
2020-03-30 16:37:56
46.38.145.4 attackbots
(smtpauth) Failed SMTP AUTH login from 46.38.145.4 (GB/United Kingdom/-): 5 in the last 3600 secs
2020-03-30 16:24:07
52.148.80.180 attackspambots
Port probing on unauthorized port 22
2020-03-30 16:38:43
106.13.6.116 attackbots
Mar 30 08:34:42 internal-server-tf sshd\[9582\]: Invalid user ppk from 106.13.6.116Mar 30 08:36:49 internal-server-tf sshd\[9632\]: Invalid user ppk from 106.13.6.116
...
2020-03-30 16:37:05
14.192.241.109 attackspambots
Unauthorized connection attempt detected from IP address 14.192.241.109 to port 23 [T]
2020-03-30 16:24:55
180.183.68.87 attack
Honeypot attack, port: 445, PTR: mx-ll-180.183.68-87.dynamic.3bb.in.th.
2020-03-30 16:51:03
123.21.150.187 attack
20/3/29@23:52:56: FAIL: Alarm-Network address from=123.21.150.187
...
2020-03-30 16:09:38
134.175.93.141 attackspam
Mar 30 09:18:13 ns382633 sshd\[19576\]: Invalid user gid from 134.175.93.141 port 33232
Mar 30 09:18:13 ns382633 sshd\[19576\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.93.141
Mar 30 09:18:15 ns382633 sshd\[19576\]: Failed password for invalid user gid from 134.175.93.141 port 33232 ssh2
Mar 30 09:27:05 ns382633 sshd\[21334\]: Invalid user jgu from 134.175.93.141 port 39804
Mar 30 09:27:05 ns382633 sshd\[21334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.93.141
2020-03-30 16:48:18
93.149.12.2 attackbots
fail2ban -- 93.149.12.2
...
2020-03-30 16:55:03
60.246.1.99 attackbots
(imapd) Failed IMAP login from 60.246.1.99 (MO/Macao/nz1l99.bb60246.ctm.net): 1 in the last 3600 secs
2020-03-30 16:53:24

Recently Reported IPs

104.18.42.225 104.18.42.233 246.128.97.56 104.18.42.234
104.18.42.236 104.18.42.237 93.141.186.159 104.18.42.247
104.18.42.25 104.18.42.253 104.18.42.27 145.49.22.114
10.29.72.16 104.18.42.32 104.18.42.33 82.4.81.67
184.228.131.202 2.218.10.168 113.144.87.238 104.18.42.37