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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;49.252.164.89.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 09:23:08 CST 2020
;; MSG SIZE  rcvd: 117
Host info
89.164.252.49.in-addr.arpa domain name pointer em49-252-164-89.pool.e-mobile.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
89.164.252.49.in-addr.arpa	name = em49-252-164-89.pool.e-mobile.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
46.171.110.250 attack
Autoban   46.171.110.250 AUTH/CONNECT
2019-12-13 05:55:23
159.89.232.144 attackspambots
Wordpress xmlrpc
2019-12-13 05:49:41
193.188.22.229 attackbots
Dec 12 20:53:03 XXX sshd[1671]: Invalid user james from 193.188.22.229 port 58111
2019-12-13 05:34:39
89.248.160.193 attack
Dec 13 00:01:44 debian-2gb-vpn-nbg1-1 kernel: [562882.970211] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=89.248.160.193 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=39629 PROTO=TCP SPT=57899 DPT=5971 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-13 05:38:55
51.83.42.108 attackspam
2019-12-12 06:03:33 server sshd[56196]: Failed password for invalid user jolly from 51.83.42.108 port 35728 ssh2
2019-12-13 05:23:49
46.22.49.41 attack
Autoban   46.22.49.41 AUTH/CONNECT
2019-12-13 05:48:53
49.245.126.193 attackspam
Autoban   49.245.126.193 AUTH/CONNECT
2019-12-13 05:33:57
114.43.190.127 attack
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2019-12-13 05:38:28
49.49.212.222 attack
Autoban   49.49.212.222 AUTH/CONNECT
2019-12-13 05:30:58
46.180.141.150 attack
Autoban   46.180.141.150 AUTH/CONNECT
2019-12-13 05:53:09
68.183.233.171 attack
Fail2Ban - SSH Bruteforce Attempt
2019-12-13 05:46:13
49.0.32.218 attackspambots
Autoban   49.0.32.218 AUTH/CONNECT
2019-12-13 05:37:18
119.28.66.152 attackspam
Dec 12 20:29:43 loxhost sshd\[14532\]: Invalid user admin from 119.28.66.152 port 53100
Dec 12 20:29:43 loxhost sshd\[14532\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.66.152
Dec 12 20:29:45 loxhost sshd\[14532\]: Failed password for invalid user admin from 119.28.66.152 port 53100 ssh2
Dec 12 20:36:08 loxhost sshd\[14738\]: Invalid user higginbotham from 119.28.66.152 port 34052
Dec 12 20:36:08 loxhost sshd\[14738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.66.152
...
2019-12-13 05:30:28
5.133.66.109 attack
Autoban   5.133.66.109 AUTH/CONNECT
2019-12-13 05:25:12
46.41.150.10 attackspam
Autoban   46.41.150.10 AUTH/CONNECT
2019-12-13 05:41:09

Recently Reported IPs

200.108.82.84 44.149.109.130 248.246.234.167 116.234.188.214
45.176.214.185 74.164.89.231 192.157.219.89 45.176.214.154
65.34.69.248 107.64.74.185 45.242.19.4 115.162.155.85
49.197.40.25 180.123.137.150 196.149.212.184 219.134.106.116
207.87.195.116 210.16.88.122 148.227.236.68 80.62.3.77