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

;; QUESTION SECTION:
;104.21.76.69.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:55:55 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 69.76.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 69.76.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
159.89.114.40 attackspam
Feb 19 15:33:54 MK-Soft-VM8 sshd[31017]: Failed password for proxy from 159.89.114.40 port 38688 ssh2
...
2020-02-20 03:07:19
78.201.12.180 attackspambots
2020-02-19T14:33:28.968905  sshd[27032]: Invalid user jira from 78.201.12.180 port 50676
2020-02-19T14:33:28.982776  sshd[27032]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.201.12.180
2020-02-19T14:33:28.968905  sshd[27032]: Invalid user jira from 78.201.12.180 port 50676
2020-02-19T14:33:30.993132  sshd[27032]: Failed password for invalid user jira from 78.201.12.180 port 50676 ssh2
...
2020-02-20 02:58:07
187.44.92.249 attackbotsspam
Honeypot attack, port: 445, PTR: 187-44-92-249.dynamic.rede.tritelecom.com.br.
2020-02-20 02:59:20
94.102.56.181 attackbotsspam
Feb 19 19:31:52 debian-2gb-nbg1-2 kernel: \[4396324.901633\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.102.56.181 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=23199 PROTO=TCP SPT=57510 DPT=4115 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-20 03:05:02
51.158.113.27 attackbots
5x Failed Password
2020-02-20 02:58:57
31.133.58.26 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-20 02:50:41
94.103.120.200 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-20 03:00:37
2600:3c01::f03c:91ff:fe96:e6f9 attackbots
xmlrpc attack
2020-02-20 03:01:05
93.94.187.20 attackbots
20/2/19@08:33:41: FAIL: IoT-Telnet address from=93.94.187.20
...
2020-02-20 02:47:01
5.243.212.115 attackspam
Honeypot attack, port: 5555, PTR: m5-243-212-115.cust.tele2.se.
2020-02-20 02:52:58
51.105.19.153 attackbots
Unauthorised access (Feb 19) SRC=51.105.19.153 LEN=40 TTL=53 ID=48229 TCP DPT=23 WINDOW=64598 SYN 
Unauthorised access (Feb 16) SRC=51.105.19.153 LEN=40 TTL=51 ID=12530 TCP DPT=23 WINDOW=31235 SYN
2020-02-20 03:22:32
95.43.7.174 attackbotsspam
Honeypot attack, port: 5555, PTR: 95-43-7-174.ip.btc-net.bg.
2020-02-20 03:06:17
80.26.100.226 attackspam
20/2/19@09:32:30: FAIL: Alarm-Network address from=80.26.100.226
...
2020-02-20 03:20:03
123.31.43.40 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2020-02-20 02:51:43
43.255.172.108 attackbotsspam
Honeypot attack, port: 81, PTR: PTR record not found
2020-02-20 03:05:40

Recently Reported IPs

104.21.76.75 104.21.76.76 104.21.76.77 104.21.76.72
104.21.76.74 104.21.76.70 104.21.76.79 104.21.76.78
104.21.76.8 104.21.76.80 104.21.76.85 104.21.76.88
104.21.76.87 104.21.76.90 104.21.76.86 104.21.76.95
104.21.76.89 104.21.76.92 104.21.76.91 104.21.76.96