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

;; QUESTION SECTION:
;104.18.19.114.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 05:20:06 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 114.19.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 114.19.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
110.138.74.87 attackbotsspam
DATE:2019-10-18 06:38:32, IP:110.138.74.87, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2019-10-18 18:05:36
103.76.252.6 attackbots
Invalid user cuigj from 103.76.252.6 port 18146
2019-10-18 18:14:40
171.119.184.17 attackspam
Unauthorised access (Oct 18) SRC=171.119.184.17 LEN=40 TTL=49 ID=53348 TCP DPT=8080 WINDOW=25669 SYN 
Unauthorised access (Oct 17) SRC=171.119.184.17 LEN=40 TTL=49 ID=40633 TCP DPT=8080 WINDOW=25669 SYN 
Unauthorised access (Oct 16) SRC=171.119.184.17 LEN=40 TTL=49 ID=62491 TCP DPT=8080 WINDOW=46056 SYN 
Unauthorised access (Oct 15) SRC=171.119.184.17 LEN=40 TTL=49 ID=3643 TCP DPT=8080 WINDOW=25669 SYN 
Unauthorised access (Oct 15) SRC=171.119.184.17 LEN=40 TTL=49 ID=45878 TCP DPT=8080 WINDOW=25669 SYN
2019-10-18 17:56:20
158.69.210.117 attackspam
v+ssh-bruteforce
2019-10-18 17:41:42
72.31.40.122 attackspambots
Automatic report - Port Scan Attack
2019-10-18 17:42:15
47.40.20.138 attack
$f2bV_matches
2019-10-18 18:03:19
142.93.235.47 attack
Oct 18 06:33:55 firewall sshd[6320]: Failed password for invalid user stream from 142.93.235.47 port 43714 ssh2
Oct 18 06:37:15 firewall sshd[6432]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.235.47  user=root
Oct 18 06:37:17 firewall sshd[6432]: Failed password for root from 142.93.235.47 port 54738 ssh2
...
2019-10-18 18:12:57
220.142.51.136 attack
Unauthorised access (Oct 18) SRC=220.142.51.136 LEN=40 PREC=0x20 TTL=51 ID=15306 TCP DPT=23 WINDOW=34725 SYN
2019-10-18 17:52:31
185.156.73.42 attackbotsspam
Port scan on 6 port(s): 3709 3710 3711 40834 42115 42117
2019-10-18 17:59:55
217.218.21.242 attackspam
Automatic report - SSH Brute-Force Attack
2019-10-18 18:08:35
113.125.25.73 attack
Automatic report - Banned IP Access
2019-10-18 18:15:40
222.186.173.180 attackspam
Oct 18 05:50:52 ny01 sshd[6158]: Failed password for root from 222.186.173.180 port 63044 ssh2
Oct 18 05:51:08 ny01 sshd[6158]: error: maximum authentication attempts exceeded for root from 222.186.173.180 port 63044 ssh2 [preauth]
Oct 18 05:51:18 ny01 sshd[6191]: Failed password for root from 222.186.173.180 port 12414 ssh2
2019-10-18 17:58:52
138.197.36.189 attackbots
SSH Brute-Force reported by Fail2Ban
2019-10-18 18:18:25
54.208.201.249 attack
port scan and connect, tcp 80 (http)
2019-10-18 17:47:00
58.51.219.19 attack
Automatic report - Port Scan
2019-10-18 18:05:22

Recently Reported IPs

104.18.188.23 104.18.19.240 104.18.19.161 104.18.192.226
104.18.19.177 104.18.19.203 104.18.192.12 104.18.197.20
104.18.193.12 104.18.198.20 104.18.199.20 104.18.196.20
104.18.2.196 104.18.193.226 104.18.2.31 104.18.2.154
104.18.2.201 104.18.199.238 104.18.2.11 104.18.2.238