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

;; QUESTION SECTION:
;104.18.79.2.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 05:54:48 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 2.79.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 2.79.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.180.142 attackbotsspam
Jan  8 17:34:30 localhost sshd\[101276\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.142  user=root
Jan  8 17:34:33 localhost sshd\[101276\]: Failed password for root from 222.186.180.142 port 61981 ssh2
Jan  8 17:34:36 localhost sshd\[101276\]: Failed password for root from 222.186.180.142 port 61981 ssh2
Jan  8 17:34:38 localhost sshd\[101276\]: Failed password for root from 222.186.180.142 port 61981 ssh2
Jan  8 17:45:08 localhost sshd\[101467\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.142  user=root
...
2020-01-09 01:46:05
39.42.97.148 attackbots
Unauthorized connection attempt detected from IP address 39.42.97.148 to port 1433 [T]
2020-01-09 01:44:10
175.4.222.69 attackspambots
Unauthorized connection attempt detected from IP address 175.4.222.69 to port 23 [T]
2020-01-09 01:51:06
114.229.141.119 attack
Unauthorized connection attempt detected from IP address 114.229.141.119 to port 2323 [T]
2020-01-09 01:57:32
115.146.123.38 attackbotsspam
Unauthorized connection attempt detected from IP address 115.146.123.38 to port 3389 [T]
2020-01-09 01:56:49
134.175.161.251 attackspam
invalid user
2020-01-09 01:29:31
118.232.56.166 attack
Unauthorized connection attempt detected from IP address 118.232.56.166 to port 23 [T]
2020-01-09 01:32:38
111.35.152.114 attackbotsspam
Unauthorized connection attempt detected from IP address 111.35.152.114 to port 23 [T]
2020-01-09 02:00:05
59.110.231.195 attackspambots
Unauthorized connection attempt detected from IP address 59.110.231.195 to port 22 [T]
2020-01-09 02:03:29
111.34.117.108 attackspambots
Unauthorized connection attempt detected from IP address 111.34.117.108 to port 23 [T]
2020-01-09 01:37:16
183.91.195.200 attackspambots
Unauthorized connection attempt detected from IP address 183.91.195.200 to port 23 [T]
2020-01-09 01:49:10
178.205.254.22 attackbotsspam
Unauthorized connection attempt detected from IP address 178.205.254.22 to port 81 [T]
2020-01-09 01:28:35
114.67.100.57 attackbots
Unauthorized connection attempt detected from IP address 114.67.100.57 to port 1433 [T]
2020-01-09 01:35:44
85.95.153.59 attackspambots
Unauthorized connection attempt detected from IP address 85.95.153.59 to port 445 [T]
2020-01-09 02:02:11
106.249.156.18 attack
Unauthorized connection attempt detected from IP address 106.249.156.18 to port 4567 [T]
2020-01-09 01:38:20

Recently Reported IPs

182.180.44.58 104.18.8.127 104.18.8.13 104.18.8.131
104.18.8.134 104.18.8.137 104.18.8.15 104.18.8.152
104.18.8.164 104.18.8.165 104.18.8.167 245.20.134.65
104.18.8.171 104.18.8.174 104.18.8.199 104.18.8.217
104.18.8.22 104.18.8.238 104.18.8.239 104.18.8.31