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

;; QUESTION SECTION:
;104.21.14.92.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:11:38 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 92.14.21.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 92.14.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
41.236.172.241 attackspam
Unauthorized connection attempt detected from IP address 41.236.172.241 to port 22 [J]
2020-01-22 07:56:00
65.98.111.218 botsattack
Jan 22 00:03:35 s2 sshd[30879]: reverse mapping checking getaddrinfo for atalanta.umpi.edu [65.98.111.218] failed - POSSIBLE BREAK-IN ATTEMPT!
Jan 22 00:03:35 s2 sshd[30879]: Invalid user twintown from 65.98.111.218
Jan 22 00:03:35 s2 sshd[30879]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=65.98.111.218
Jan 22 00:03:37 s2 sshd[30879]: Failed password for invalid user twintown from 65.98.111.218 port 43018 ssh2
Jan 22 00:03:37 s2 sshd[30879]: Received disconnect from 65.98.111.218: 11: Bye Bye [preauth]
2020-01-22 08:06:25
121.121.78.211 attackbots
Unauthorized connection attempt detected from IP address 121.121.78.211 to port 81 [J]
2020-01-22 08:08:43
179.51.248.135 attackbotsspam
Unauthorized connection attempt detected from IP address 179.51.248.135 to port 4873 [J]
2020-01-22 08:03:05
95.238.191.243 attackbotsspam
Unauthorized connection attempt detected from IP address 95.238.191.243 to port 80 [J]
2020-01-22 08:13:14
220.200.167.206 attack
Unauthorized connection attempt detected from IP address 220.200.167.206 to port 8118 [J]
2020-01-22 08:22:45
106.45.1.37 attackbotsspam
Unauthorized connection attempt detected from IP address 106.45.1.37 to port 8123 [J]
2020-01-22 08:12:04
219.78.126.108 attack
Unauthorized connection attempt detected from IP address 219.78.126.108 to port 5555 [J]
2020-01-22 07:59:01
197.35.12.149 attackbotsspam
Unauthorized connection attempt detected from IP address 197.35.12.149 to port 23 [J]
2020-01-22 08:00:44
111.224.218.212 attackspambots
Unauthorized connection attempt detected from IP address 111.224.218.212 to port 8888 [T]
2020-01-22 08:10:59
167.114.113.141 attack
Unauthorized connection attempt detected from IP address 167.114.113.141 to port 2220 [J]
2020-01-22 08:06:02
94.247.248.133 attackbots
Unauthorized connection attempt detected from IP address 94.247.248.133 to port 80 [J]
2020-01-22 08:13:40
150.109.170.192 attack
Unauthorized connection attempt detected from IP address 150.109.170.192 to port 6103 [J]
2020-01-22 08:06:49
150.116.35.4 attackspambots
Unauthorized connection attempt detected from IP address 150.116.35.4 to port 23 [J]
2020-01-22 08:06:34
75.69.35.123 attackspambots
Unauthorized connection attempt detected from IP address 75.69.35.123 to port 22 [J]
2020-01-22 08:17:07

Recently Reported IPs

104.21.14.9 104.21.14.85 104.21.15.106 104.21.67.31
104.21.15.11 104.21.15.109 104.21.15.111 104.21.15.136
104.21.15.121 104.21.15.139 104.21.15.138 104.21.15.143
104.21.15.140 104.21.15.141 104.21.67.34 104.21.15.142
104.21.15.144 104.21.15.145 104.21.15.146 104.21.15.147