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.83.14 attackspam
firewall-block, port(s): 61867/tcp
2020-01-14 08:56:22
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.18.8.118
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25519
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.18.8.118.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 08:25:30 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 118.8.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 118.8.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.39.164.58 attackbotsspam
Wordpress login attempts
2020-03-22 20:16:08
41.146.133.194 attack
port 23
2020-03-22 20:11:39
94.41.108.182 attackspambots
" "
2020-03-22 20:51:31
165.227.80.114 attackbotsspam
Mar 22 12:07:14 debian-2gb-nbg1-2 kernel: \[7134327.634668\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=165.227.80.114 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=9879 PROTO=TCP SPT=47319 DPT=29497 WINDOW=1024 RES=0x00 SYN URGP=0
2020-03-22 20:43:42
79.10.35.178 attackbots
Unauthorized connection attempt detected from IP address 79.10.35.178 to port 80
2020-03-22 20:11:02
171.227.7.169 attack
Scanning
2020-03-22 20:13:21
167.114.103.140 attackbotsspam
Mar 22 10:38:12 XXXXXX sshd[43595]: Invalid user xl from 167.114.103.140 port 36474
2020-03-22 20:18:03
167.71.128.144 attackbots
Mar 22 06:08:22 * sshd[7259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.128.144
Mar 22 06:08:24 * sshd[7259]: Failed password for invalid user wb from 167.71.128.144 port 50406 ssh2
2020-03-22 20:37:26
41.237.90.132 attackspam
port 23
2020-03-22 20:09:35
89.248.172.85 attackspam
firewall-block, port(s): 3637/tcp, 3805/tcp, 3980/tcp, 64000/tcp
2020-03-22 20:40:37
106.13.98.119 attackspam
Mar 22 13:13:04 vpn01 sshd[12700]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.98.119
Mar 22 13:13:06 vpn01 sshd[12700]: Failed password for invalid user jialiang from 106.13.98.119 port 42782 ssh2
...
2020-03-22 20:42:39
77.253.229.101 attack
Automatic report - Port Scan Attack
2020-03-22 20:43:04
106.13.19.145 attackspambots
SSH login attempts.
2020-03-22 20:17:12
37.233.22.124 attackspam
port 23
2020-03-22 20:15:19
80.85.154.247 attackbotsspam
Sun Mar 22 04:47:34 2020 \[pid 28177\] \[ftp\] FAIL LOGIN: Client "80.85.154.247"
Sun Mar 22 04:47:37 2020 \[pid 28179\] \[anyone\] FAIL LOGIN: Client "80.85.154.247"
Sun Mar 22 04:47:41 2020 \[pid 28201\] \[PlcmSpIp\] FAIL LOGIN: Client "80.85.154.247"
Sun Mar 22 04:47:41 2020 \[pid 28247\] \[admin\] FAIL LOGIN: Client "80.85.154.247"
Sun Mar 22 04:47:45 2020 \[pid 28251\] \[PlcmSpIp\] FAIL LOGIN: Client "80.85.154.247"
Sun Mar 22 04:47:45 2020 \[pid 28253\] \[admin\] FAIL LOGIN: Client "80.85.154.247"
2020-03-22 20:29:44

Recently Reported IPs

104.18.7.212 125.212.225.224 104.18.8.189 104.18.73.1
104.18.8.125 104.18.8.243 104.18.8.45 104.18.89.236
104.18.9.111 104.18.8.214 104.18.88.236 104.18.8.223
104.18.9.118 104.18.9.125 104.18.9.12 125.212.232.165
104.18.9.189 125.212.243.110 104.18.9.214 104.18.9.223