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: Japan

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

;; QUESTION SECTION:
;221.80.94.244.			IN	A

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

;; Query time: 32 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 13:28:25 CST 2025
;; MSG SIZE  rcvd: 106
Host info
244.94.80.221.in-addr.arpa domain name pointer softbank221080094244.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
244.94.80.221.in-addr.arpa	name = softbank221080094244.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
124.61.214.44 attack
Mar 23 10:30:46 DAAP sshd[25834]: Invalid user andrew from 124.61.214.44 port 39766
Mar 23 10:30:46 DAAP sshd[25834]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.61.214.44
Mar 23 10:30:46 DAAP sshd[25834]: Invalid user andrew from 124.61.214.44 port 39766
Mar 23 10:30:47 DAAP sshd[25834]: Failed password for invalid user andrew from 124.61.214.44 port 39766 ssh2
Mar 23 10:40:39 DAAP sshd[25957]: Invalid user refresh from 124.61.214.44 port 46874
...
2020-03-23 18:49:39
178.45.108.97 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-23 19:18:06
198.108.66.97 attack
1911/tcp 5902/tcp 4567/tcp...
[2020-01-23/03-23]17pkt,13pt.(tcp),1pt.(udp),1tp.(icmp)
2020-03-23 18:47:58
5.53.35.249 attackbotsspam
37215/tcp 37215/tcp
[2020-03-20/23]2pkt
2020-03-23 18:58:27
162.219.33.226 attack
162.219.33.226 was recorded 5 times by 4 hosts attempting to connect to the following ports: 161. Incident counter (4h, 24h, all-time): 5, 6, 13
2020-03-23 18:57:31
71.6.233.236 attack
5431/tcp 139/tcp 110/tcp...
[2020-01-24/03-23]6pkt,5pt.(tcp),1pt.(udp)
2020-03-23 19:22:02
195.211.87.139 attackbotsspam
445/tcp 445/tcp
[2020-03-20/23]2pkt
2020-03-23 19:08:39
40.115.60.71 attack
Automatic report - XMLRPC Attack
2020-03-23 18:58:01
103.95.41.9 attackbotsspam
$f2bV_matches
2020-03-23 19:15:40
94.45.57.78 attackspam
Mar 23 10:21:54 hosting180 sshd[2140]: Invalid user gq from 94.45.57.78 port 45688
...
2020-03-23 19:13:37
50.209.172.76 attackbotsspam
...
2020-03-23 19:01:56
41.237.127.209 attack
scan z
2020-03-23 19:23:44
173.0.58.202 attackbots
173.0.58.202 was recorded 5 times by 5 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 5, 8, 9
2020-03-23 18:48:29
182.58.233.91 attackspambots
445/tcp
[2020-03-23]1pkt
2020-03-23 19:24:03
220.169.119.88 attackbots
[Wed Mar 04 03:16:44 2020] - Syn Flood From IP: 220.169.119.88 Port: 6000
2020-03-23 19:02:15

Recently Reported IPs

176.83.66.237 108.242.158.126 142.149.61.232 46.137.92.35
181.161.209.219 229.84.200.133 73.172.35.71 36.1.66.124
49.39.44.225 157.241.76.167 221.199.81.204 87.254.73.170
231.93.11.10 184.80.157.170 237.249.87.222 255.152.134.215
248.74.172.188 237.58.172.180 99.135.235.43 168.196.172.247