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 of America (the)

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

;; QUESTION SECTION:
;8.100.221.80.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 01 01:16:05 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 80.221.100.8.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 80.221.100.8.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
138.219.192.98 attack
Nov 25 07:25:51 lnxmail61 sshd[21311]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.219.192.98
2019-11-25 18:16:03
178.128.110.195 attackbotsspam
Automatic report - XMLRPC Attack
2019-11-25 18:16:17
97.87.244.154 attack
Nov 25 10:46:38 hosting sshd[20075]: Invalid user rmsadm from 97.87.244.154 port 41943
...
2019-11-25 18:28:43
49.235.243.246 attack
SSH Brute Force, server-1 sshd[12090]: Failed password for invalid user masjadi from 49.235.243.246 port 52936 ssh2
2019-11-25 18:29:49
182.61.132.165 attack
Nov 25 15:09:44 itv-usvr-01 sshd[2833]: Invalid user miquela from 182.61.132.165
2019-11-25 18:23:29
140.143.137.44 attackspambots
Nov 25 07:21:42 sd-53420 sshd\[18737\]: Invalid user chronicles from 140.143.137.44
Nov 25 07:21:42 sd-53420 sshd\[18737\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.137.44
Nov 25 07:21:45 sd-53420 sshd\[18737\]: Failed password for invalid user chronicles from 140.143.137.44 port 51720 ssh2
Nov 25 07:25:18 sd-53420 sshd\[19245\]: Invalid user oracle from 140.143.137.44
Nov 25 07:25:18 sd-53420 sshd\[19245\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.137.44
...
2019-11-25 18:35:25
200.169.223.98 attackspambots
Nov 25 10:35:34 sbg01 sshd[27017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.169.223.98
Nov 25 10:35:37 sbg01 sshd[27017]: Failed password for invalid user guest from 200.169.223.98 port 40286 ssh2
Nov 25 10:40:02 sbg01 sshd[27044]: Failed password for uucp from 200.169.223.98 port 47460 ssh2
2019-11-25 18:27:23
62.159.228.138 attack
Automatic report - Banned IP Access
2019-11-25 18:22:40
129.213.194.201 attackbotsspam
[Aegis] @ 2019-11-25 08:43:14  0000 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2019-11-25 18:38:57
173.212.252.245 attack
...
2019-11-25 18:30:33
187.188.251.219 attackbotsspam
*Port Scan* detected from 187.188.251.219 (MX/Mexico/fixed-187-188-251-219.totalplay.net). 4 hits in the last 80 seconds
2019-11-25 18:49:45
190.145.39.36 attack
Automatic report - Banned IP Access
2019-11-25 18:34:26
193.31.24.113 attackbotsspam
11/25/2019-11:40:02.846433 193.31.24.113 Protocol: 6 SURICATA TLS invalid record/traffic
2019-11-25 18:46:41
91.142.222.245 attackbotsspam
Invalid user admin from 91.142.222.245 port 45576
2019-11-25 18:36:01
77.247.109.41 attack
SIPVicious Scanner Detection
2019-11-25 18:26:20

Recently Reported IPs

190.187.222.121 72.71.201.77 4.217.182.136 184.254.113.238
122.66.193.53 70.255.120.142 121.31.24.176 44.128.216.87
249.183.223.62 158.116.90.206 115.88.2.14 229.152.206.232
22.253.227.91 232.200.108.200 113.30.212.220 180.117.114.67
148.179.202.190 43.95.129.159 104.40.64.9 97.229.133.158