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

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

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

;; Query time: 4 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Mon May 27 13:14:00 CST 2019
;; MSG SIZE  rcvd: 116

Host info
9.114.135.49.in-addr.arpa domain name pointer w0109-49-135-114-9.uqwimax.jp.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
9.114.135.49.in-addr.arpa	name = w0109-49-135-114-9.uqwimax.jp.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
179.57.254.69 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2019-10-26 06:53:21
159.203.201.108 attackbots
8123/tcp 21768/tcp 2525/tcp...
[2019-09-12/10-24]44pkt,37pt.(tcp),3pt.(udp)
2019-10-26 06:40:43
182.72.0.250 attackbotsspam
Invalid user pass from 182.72.0.250 port 40260
2019-10-26 06:35:36
184.30.210.217 attackspam
10/25/2019-23:57:38.301500 184.30.210.217 Protocol: 6 SURICATA TLS invalid record/traffic
2019-10-26 06:33:56
106.12.21.212 attackbotsspam
Oct 25 20:26:07 *** sshd[1885]: User root from 106.12.21.212 not allowed because not listed in AllowUsers
2019-10-26 06:35:49
192.144.174.51 attackbotsspam
Invalid user sa from 192.144.174.51 port 57768
2019-10-26 06:30:39
78.169.207.219 attackbots
ENG,WP GET /wp-login.php
2019-10-26 06:43:30
112.175.124.90 attackspambots
slow and persistent scanner
2019-10-26 06:22:12
106.38.62.126 attackbots
Oct 25 23:28:57 MK-Soft-VM6 sshd[13081]: Failed password for root from 106.38.62.126 port 25269 ssh2
Oct 25 23:32:35 MK-Soft-VM6 sshd[13093]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.38.62.126 
...
2019-10-26 06:33:40
77.72.148.89 attackspam
Lines containing failures of 77.72.148.89
Oct 24 14:19:19 shared02 sshd[11243]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.72.148.89  user=r.r
Oct 24 14:19:21 shared02 sshd[11243]: Failed password for r.r from 77.72.148.89 port 42252 ssh2
Oct 24 14:19:21 shared02 sshd[11243]: Received disconnect from 77.72.148.89 port 42252:11: Bye Bye [preauth]
Oct 24 14:19:21 shared02 sshd[11243]: Disconnected from authenticating user r.r 77.72.148.89 port 42252 [preauth]
Oct 24 15:18:27 shared02 sshd[24374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.72.148.89  user=r.r
Oct 24 15:18:29 shared02 sshd[24374]: Failed password for r.r from 77.72.148.89 port 47052 ssh2
Oct 24 15:18:29 shared02 sshd[24374]: Received disconnect from 77.72.148.89 port 47052:11: Bye Bye [preauth]
Oct 24 15:18:29 shared02 sshd[24374]: Disconnected from authenticating user r.r 77.72.148.89 port 47052 [preauth]
Oct 24 ........
------------------------------
2019-10-26 06:29:10
46.22.224.50 attackspambots
ET CINS Active Threat Intelligence Poor Reputation IP group 33 - port: 1433 proto: TCP cat: Misc Attack
2019-10-26 06:46:19
165.227.18.169 attackspam
Oct 25 10:18:36 web1 sshd\[24951\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.18.169  user=root
Oct 25 10:18:39 web1 sshd\[24951\]: Failed password for root from 165.227.18.169 port 41068 ssh2
Oct 25 10:22:37 web1 sshd\[25298\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.18.169  user=root
Oct 25 10:22:39 web1 sshd\[25298\]: Failed password for root from 165.227.18.169 port 51428 ssh2
Oct 25 10:26:35 web1 sshd\[25642\]: Invalid user data from 165.227.18.169
Oct 25 10:26:35 web1 sshd\[25642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.18.169
2019-10-26 06:23:35
139.155.1.250 attackbotsspam
2019-10-25T22:21:11.022447shield sshd\[6438\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.1.250  user=root
2019-10-25T22:21:12.832196shield sshd\[6438\]: Failed password for root from 139.155.1.250 port 38250 ssh2
2019-10-25T22:25:20.657297shield sshd\[7325\]: Invalid user bess from 139.155.1.250 port 45472
2019-10-25T22:25:20.661475shield sshd\[7325\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.1.250
2019-10-25T22:25:22.787660shield sshd\[7325\]: Failed password for invalid user bess from 139.155.1.250 port 45472 ssh2
2019-10-26 06:34:25
185.176.27.30 attack
firewall-block, port(s): 2494/tcp
2019-10-26 06:51:44
159.203.201.125 attackbotsspam
ET DROP Dshield Block Listed Source group 1 - port: 512 proto: TCP cat: Misc Attack
2019-10-26 06:54:26

Recently Reported IPs

213.151.13.158 38.196.161.222 118.243.61.146 190.201.189.255
224.108.106.214 134.175.0.75 72.124.123.159 85.50.208.112
56.242.184.77 247.136.31.59 70.117.46.126 22.220.220.152
168.99.127.194 107.57.104.34 115.216.116.163 139.213.74.75
211.158.73.188 35.125.236.91 184.44.39.231 142.93.190.15