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

;; QUESTION SECTION:
;113.42.36.48.			IN	A

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

;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 16:41:14 CST 2022
;; MSG SIZE  rcvd: 105
Host info
48.36.42.113.in-addr.arpa domain name pointer 113x42x36x48.ap113.ftth.ucom.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
48.36.42.113.in-addr.arpa	name = 113x42x36x48.ap113.ftth.ucom.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
112.85.42.173 attack
v+ssh-bruteforce
2020-02-09 22:21:42
41.47.29.211 attackspambots
20/2/9@08:37:39: FAIL: IoT-Telnet address from=41.47.29.211
...
2020-02-09 21:51:37
222.252.63.13 attackspambots
445/tcp 445/tcp 445/tcp...
[2020-02-07/08]4pkt,1pt.(tcp)
2020-02-09 22:35:12
90.232.65.34 attackbots
Fail2Ban Ban Triggered
2020-02-09 22:27:49
198.108.66.90 attackbots
8088/tcp 20000/tcp 8883/tcp...
[2019-12-16/2020-02-09]9pkt,9pt.(tcp)
2020-02-09 22:21:07
49.88.112.74 attack
5x Failed Password
2020-02-09 22:06:22
132.232.113.102 attackspambots
Feb  9 15:08:34 silence02 sshd[1946]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.113.102
Feb  9 15:08:36 silence02 sshd[1946]: Failed password for invalid user hkh from 132.232.113.102 port 33554 ssh2
Feb  9 15:13:11 silence02 sshd[2193]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.113.102
2020-02-09 22:28:08
95.9.185.37 attackspambots
Unauthorized connection attempt detected from IP address 95.9.185.37 to port 445
2020-02-09 22:25:31
106.13.224.130 attack
Feb  9 13:37:28 ws26vmsma01 sshd[9540]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.224.130
Feb  9 13:37:30 ws26vmsma01 sshd[9540]: Failed password for invalid user aad from 106.13.224.130 port 39912 ssh2
...
2020-02-09 22:01:29
180.176.105.41 attack
23/tcp 81/tcp
[2020-01-08/02-09]2pkt
2020-02-09 21:55:51
96.80.251.85 attack
23/tcp 37215/tcp...
[2019-12-22/2020-02-09]8pkt,2pt.(tcp)
2020-02-09 22:11:06
89.248.168.41 attackspam
trying to access non-authorized port
2020-02-09 21:53:54
118.24.81.234 attackbots
Feb  9 14:37:20 lnxmysql61 sshd[15702]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.81.234
Feb  9 14:37:20 lnxmysql61 sshd[15702]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.81.234
2020-02-09 22:10:48
106.52.246.170 attack
Feb  9 14:34:05 legacy sshd[30794]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.246.170
Feb  9 14:34:08 legacy sshd[30794]: Failed password for invalid user knz from 106.52.246.170 port 39108 ssh2
Feb  9 14:37:44 legacy sshd[30944]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.246.170
...
2020-02-09 21:48:25
181.49.107.162 attack
SSH invalid-user multiple login try
2020-02-09 22:23:32

Recently Reported IPs

101.0.54.51 151.242.25.81 36.106.167.246 115.60.166.250
122.234.36.173 178.208.255.139 58.27.227.10 51.253.38.215
201.230.37.223 213.159.216.144 54.177.167.228 191.240.114.107
20.120.45.212 45.83.65.61 119.60.255.30 223.149.253.46
42.225.10.217 66.117.211.106 89.212.145.28 113.120.29.223