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

Region: Hokkaidō

Country: Japan

Internet Service Provider: KDDI Corporation

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

;; QUESTION SECTION:
;113.159.147.166.		IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 04 17:54:23 CST 2024
;; MSG SIZE  rcvd: 108
Host info
166.147.159.113.in-addr.arpa domain name pointer KD113159147166.ppp-bb.dion.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
166.147.159.113.in-addr.arpa	name = KD113159147166.ppp-bb.dion.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
46.101.105.55 attackspam
SSH Brute Force, server-1 sshd[9044]: Failed password for invalid user bigbomber from 46.101.105.55 port 60394 ssh2
2019-12-23 23:37:52
39.33.98.169 attackspambots
Automatic report - Port Scan Attack
2019-12-23 23:55:37
139.59.84.111 attackbotsspam
Jul 25 19:52:39 yesfletchmain sshd\[18041\]: Invalid user princess from 139.59.84.111 port 50184
Jul 25 19:52:39 yesfletchmain sshd\[18041\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.84.111
Jul 25 19:52:41 yesfletchmain sshd\[18041\]: Failed password for invalid user princess from 139.59.84.111 port 50184 ssh2
Jul 25 19:57:42 yesfletchmain sshd\[18355\]: Invalid user admin from 139.59.84.111 port 44754
Jul 25 19:57:42 yesfletchmain sshd\[18355\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.84.111
...
2019-12-23 23:58:34
124.156.62.116 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-24 00:09:54
13.113.152.0 attack
Feb 25 18:27:45 dillonfme sshd\[29523\]: Invalid user piotr from 13.113.152.0 port 58432
Feb 25 18:27:45 dillonfme sshd\[29523\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.113.152.0
Feb 25 18:27:47 dillonfme sshd\[29523\]: Failed password for invalid user piotr from 13.113.152.0 port 58432 ssh2
Feb 25 18:33:02 dillonfme sshd\[29797\]: Invalid user teamspeak3 from 13.113.152.0 port 57024
Feb 25 18:33:02 dillonfme sshd\[29797\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.113.152.0
...
2019-12-23 23:42:25
110.9.166.21 attackspam
12/23/2019-09:59:30.158666 110.9.166.21 Protocol: 6 ET SCAN Potential SSH Scan
2019-12-23 23:53:11
129.28.57.8 attackbotsspam
Apr 19 18:58:40 yesfletchmain sshd\[5465\]: Invalid user qb from 129.28.57.8 port 44409
Apr 19 18:58:40 yesfletchmain sshd\[5465\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.57.8
Apr 19 18:58:42 yesfletchmain sshd\[5465\]: Failed password for invalid user qb from 129.28.57.8 port 44409 ssh2
Apr 19 19:02:05 yesfletchmain sshd\[5548\]: Invalid user vyas from 129.28.57.8 port 56950
Apr 19 19:02:05 yesfletchmain sshd\[5548\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.57.8
...
2019-12-23 23:50:21
137.74.167.250 attackspam
Dec 13 07:21:22 yesfletchmain sshd\[16277\]: Invalid user gp from 137.74.167.250 port 47572
Dec 13 07:21:22 yesfletchmain sshd\[16277\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.167.250
Dec 13 07:21:24 yesfletchmain sshd\[16277\]: Failed password for invalid user gp from 137.74.167.250 port 47572 ssh2
Dec 13 07:26:15 yesfletchmain sshd\[16333\]: Invalid user maku from 137.74.167.250 port 51673
Dec 13 07:26:15 yesfletchmain sshd\[16333\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.167.250
...
2019-12-24 00:09:19
110.52.28.32 attack
3389BruteforceFW22
2019-12-23 23:33:05
124.158.175.214 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-23 23:35:53
77.247.108.119 attack
Dec 23 15:59:47 debian-2gb-nbg1-2 kernel: \[765932.183786\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=77.247.108.119 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=65519 PROTO=TCP SPT=50910 DPT=5038 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-23 23:29:26
5.196.7.123 attackbotsspam
2019-12-23T15:09:51.526735shield sshd\[24448\]: Invalid user ching from 5.196.7.123 port 52646
2019-12-23T15:09:51.531268shield sshd\[24448\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.ip-5-196-7.eu
2019-12-23T15:09:53.388187shield sshd\[24448\]: Failed password for invalid user ching from 5.196.7.123 port 52646 ssh2
2019-12-23T15:15:04.032196shield sshd\[25638\]: Invalid user willmott from 5.196.7.123 port 56104
2019-12-23T15:15:04.037103shield sshd\[25638\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.ip-5-196-7.eu
2019-12-23 23:30:09
46.38.144.179 attackbots
Dec 23 16:37:53 relay postfix/smtpd\[8633\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 23 16:40:16 relay postfix/smtpd\[20236\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 23 16:41:04 relay postfix/smtpd\[8630\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 23 16:43:35 relay postfix/smtpd\[20028\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 23 16:44:25 relay postfix/smtpd\[8634\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-23 23:50:55
35.160.48.160 attack
12/23/2019-16:25:02.452655 35.160.48.160 Protocol: 6 SURICATA TLS invalid record/traffic
2019-12-24 00:04:50
45.143.222.167 attackbots
Brute force SMTP login attempts.
2019-12-24 00:05:59

Recently Reported IPs

113.158.63.72 113.155.249.246 113.16.16.241 113.159.191.149
113.159.11.40 113.158.183.129 209.45.224.25 113.159.61.146
210.224.249.247 113.159.7.160 113.16.202.187 113.159.94.87
113.158.195.6 113.16.43.10 113.159.10.54 113.159.35.129
113.160.182.99 113.160.190.54 113.160.225.22 151.92.46.117