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

;; QUESTION SECTION:
;49.242.206.170.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 05 15:40:59 CST 2023
;; MSG SIZE  rcvd: 107
Host info
170.206.242.49.in-addr.arpa domain name pointer 170.206.242.49.ap.yournet.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
170.206.242.49.in-addr.arpa	name = 170.206.242.49.ap.yournet.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
181.88.178.37 attack
445/tcp
[2020-02-12]1pkt
2020-02-13 06:04:13
122.117.129.143 attack
20/2/12@10:37:09: FAIL: Alarm-Network address from=122.117.129.143
20/2/12@10:37:09: FAIL: Alarm-Network address from=122.117.129.143
...
2020-02-13 05:59:02
41.90.250.217 attack
65529/tcp 1433/tcp 445/tcp...
[2020-02-10]6pkt,3pt.(tcp)
2020-02-13 05:24:23
23.129.64.234 attackspambots
Feb 12 10:39:37 ws24vmsma01 sshd[243561]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.234
Feb 12 10:39:39 ws24vmsma01 sshd[243561]: Failed password for invalid user admin from 23.129.64.234 port 45998 ssh2
...
2020-02-13 05:26:42
104.248.154.62 attackbotsspam
Telnet/23 MH Probe, BF, Hack -
2020-02-13 05:59:17
77.29.164.60 attack
Automatic report - Port Scan Attack
2020-02-13 05:50:20
218.161.76.74 attack
23/tcp 23/tcp
[2020-02-11/12]2pkt
2020-02-13 05:24:47
180.251.12.209 attackbotsspam
445/tcp
[2020-02-12]1pkt
2020-02-13 05:51:32
171.242.107.171 attack
Port probing on unauthorized port 23
2020-02-13 05:44:25
162.247.74.217 attackbotsspam
Feb 12 10:39:30 ws24vmsma01 sshd[237553]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.74.217
Feb 12 10:39:32 ws24vmsma01 sshd[237553]: Failed password for invalid user pi from 162.247.74.217 port 55860 ssh2
...
2020-02-13 05:30:46
86.57.154.175 attack
02/12/2020-08:39:29.128013 86.57.154.175 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 92
2020-02-13 05:33:27
92.63.194.108 attack
Feb 12 20:02:40 vps691689 sshd[18931]: Failed password for root from 92.63.194.108 port 35961 ssh2
Feb 12 20:02:54 vps691689 sshd[18983]: Failed none for invalid user admin from 92.63.194.108 port 37483 ssh2
...
2020-02-13 05:58:01
114.35.93.61 attackbots
Unauthorised access (Feb 12) SRC=114.35.93.61 LEN=40 TTL=45 ID=5553 TCP DPT=23 WINDOW=42699 SYN
2020-02-13 05:48:33
116.105.201.128 attack
Automatic report - Port Scan Attack
2020-02-13 05:31:02
95.110.154.101 attackbotsspam
$f2bV_matches
2020-02-13 05:57:39

Recently Reported IPs

204.181.181.90 203.57.213.34 85.71.132.230 47.122.13.128
5.55.74.219 207.165.118.23 140.123.234.99 140.116.138.61
140.116.57.210 140.116.33.22 124.17.27.171 140.113.62.132
14.102.153.210 140.116.112.4 66.96.237.182 140.116.203.93
147.8.2.30 192.235.169.212 132.170.214.13 140.116.133.163