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

;; QUESTION SECTION:
;138.64.245.71.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 12 13:30:50 CST 2022
;; MSG SIZE  rcvd: 106
Host info
71.245.64.138.in-addr.arpa domain name pointer ai245071.ppp.asahi-net.or.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
71.245.64.138.in-addr.arpa	name = ai245071.ppp.asahi-net.or.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.12.196.6 attackspam
Invalid user debian from 103.12.196.6 port 29997
2020-01-10 22:40:44
206.189.202.165 attack
Invalid user fk from 206.189.202.165 port 35086
2020-01-10 22:22:15
206.189.72.217 attackspam
Invalid user sp from 206.189.72.217 port 38342
2020-01-10 22:23:33
190.96.172.101 attackspambots
Invalid user svc from 190.96.172.101 port 44912
2020-01-10 22:26:26
106.124.137.103 attackbots
Invalid user eft from 106.124.137.103 port 48656
2020-01-10 22:39:00
180.76.246.104 attack
Invalid user evv from 180.76.246.104 port 48226
2020-01-10 22:10:25
59.175.176.233 attackspam
Unauthorized access to SSH at 10/Jan/2020:14:35:42 +0000.
2020-01-10 22:44:32
157.157.145.123 attack
Invalid user elision from 157.157.145.123 port 52252
2020-01-10 22:28:51
221.148.45.168 attack
Jan 10 13:58:36 hosting180 sshd[813]: Invalid user test from 221.148.45.168 port 52902
...
2020-01-10 22:08:41
144.217.54.51 attack
Invalid user shuai from 144.217.54.51 port 38714
2020-01-10 22:13:24
129.204.11.222 attackspam
Invalid user vo from 129.204.11.222 port 53886
2020-01-10 22:32:17
206.189.145.251 attack
Jan 10 13:48:03 powerpi2 sshd[8987]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.145.251
Jan 10 13:48:03 powerpi2 sshd[8987]: Invalid user mhx from 206.189.145.251 port 40378
Jan 10 13:48:05 powerpi2 sshd[8987]: Failed password for invalid user mhx from 206.189.145.251 port 40378 ssh2
...
2020-01-10 22:23:06
112.3.30.116 attack
Invalid user fkz from 112.3.30.116 port 49520
2020-01-10 22:15:54
124.251.110.148 attackbotsspam
(sshd) Failed SSH login from 124.251.110.148 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jan 10 14:55:28 blur sshd[11132]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.251.110.148  user=root
Jan 10 14:55:29 blur sshd[11132]: Failed password for root from 124.251.110.148 port 49448 ssh2
Jan 10 15:09:05 blur sshd[13432]: Invalid user min from 124.251.110.148 port 45094
Jan 10 15:09:06 blur sshd[13432]: Failed password for invalid user min from 124.251.110.148 port 45094 ssh2
Jan 10 15:11:16 blur sshd[13776]: Invalid user sonhn from 124.251.110.148 port 54964
2020-01-10 22:14:33
106.12.43.142 attack
01/10/2020-09:12:37.326726 106.12.43.142 Protocol: 6 ET SCAN Potential SSH Scan
2020-01-10 22:16:24

Recently Reported IPs

178.206.125.122 216.227.110.24 45.248.77.68 104.105.152.43
21.56.243.24 204.202.253.151 214.57.166.212 170.62.50.100
87.90.158.45 174.199.197.137 108.119.192.251 239.73.125.10
205.145.190.204 51.3.100.189 88.221.119.4 227.66.98.148
82.32.77.140 50.184.39.101 115.128.166.236 136.161.145.104