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

Region: Ibaraki

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

;; QUESTION SECTION:
;49.243.222.20.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 16 15:48:43 CST 2022
;; MSG SIZE  rcvd: 106
Host info
20.222.243.49.in-addr.arpa domain name pointer 20.222.243.49.ap.yournet.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.130.198.140 attackbotsspam
Aug 13 13:22:55 aat-srv002 sshd[19077]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.130.198.140
Aug 13 13:22:56 aat-srv002 sshd[19077]: Failed password for invalid user debian from 103.130.198.140 port 48104 ssh2
Aug 13 13:28:53 aat-srv002 sshd[19262]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.130.198.140
Aug 13 13:28:56 aat-srv002 sshd[19262]: Failed password for invalid user administrator from 103.130.198.140 port 40730 ssh2
...
2019-08-14 02:56:27
206.189.73.71 attackspambots
Aug 13 08:21:35 xtremcommunity sshd\[30515\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.73.71  user=root
Aug 13 08:21:37 xtremcommunity sshd\[30515\]: Failed password for root from 206.189.73.71 port 46520 ssh2
Aug 13 08:26:25 xtremcommunity sshd\[30724\]: Invalid user melk from 206.189.73.71 port 37334
Aug 13 08:26:25 xtremcommunity sshd\[30724\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.73.71
Aug 13 08:26:27 xtremcommunity sshd\[30724\]: Failed password for invalid user melk from 206.189.73.71 port 37334 ssh2
...
2019-08-14 02:22:19
114.113.221.162 attackspambots
$f2bV_matches
2019-08-14 02:16:47
149.202.59.85 attack
Aug 13 20:28:20 SilenceServices sshd[12594]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.202.59.85
Aug 13 20:28:22 SilenceServices sshd[12594]: Failed password for invalid user mmk from 149.202.59.85 port 37643 ssh2
Aug 13 20:32:30 SilenceServices sshd[15561]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.202.59.85
2019-08-14 02:44:38
42.51.34.174 attackspambots
/wp-login.php
2019-08-14 02:38:17
218.92.1.142 attackspam
Aug 13 14:37:42 TORMINT sshd\[16414\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.1.142  user=root
Aug 13 14:37:44 TORMINT sshd\[16414\]: Failed password for root from 218.92.1.142 port 18167 ssh2
Aug 13 14:38:23 TORMINT sshd\[16442\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.1.142  user=root
...
2019-08-14 02:48:19
140.143.93.31 attackspambots
Aug 13 03:37:45 vps200512 sshd\[22726\]: Invalid user chen from 140.143.93.31
Aug 13 03:37:45 vps200512 sshd\[22726\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.93.31
Aug 13 03:37:48 vps200512 sshd\[22726\]: Failed password for invalid user chen from 140.143.93.31 port 34550 ssh2
Aug 13 03:40:52 vps200512 sshd\[22829\]: Invalid user lotto from 140.143.93.31
Aug 13 03:40:52 vps200512 sshd\[22829\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.93.31
2019-08-14 02:28:22
183.245.48.250 attack
[portscan] Port scan
2019-08-14 02:46:38
153.121.57.70 attack
Aug 13 18:59:52 amit sshd\[2284\]: Invalid user hadoop from 153.121.57.70
Aug 13 18:59:52 amit sshd\[2284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=153.121.57.70
Aug 13 18:59:54 amit sshd\[2284\]: Failed password for invalid user hadoop from 153.121.57.70 port 55422 ssh2
...
2019-08-14 02:22:50
51.219.58.141 attackbotsspam
2019-08-14T01:31:24.859392enmeeting.mahidol.ac.th sshd\[30344\]: User postgres from 51.219.58.141 not allowed because not listed in AllowUsers
2019-08-14T01:31:24.873546enmeeting.mahidol.ac.th sshd\[30344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.219.58.141  user=postgres
2019-08-14T01:31:26.726259enmeeting.mahidol.ac.th sshd\[30344\]: Failed password for invalid user postgres from 51.219.58.141 port 48112 ssh2
...
2019-08-14 02:40:24
34.93.16.233 attackspambots
Splunk® : Brute-Force login attempt on SSH:
Aug 13 14:47:44 testbed sshd[5525]: Received disconnect from 34.93.16.233 port 36038:11: Bye Bye [preauth]
2019-08-14 02:50:56
93.115.28.159 attackbots
08/13/2019-03:25:14.286327 93.115.28.159 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-08-14 02:24:44
148.70.218.43 attackbots
*Port Scan* detected from 148.70.218.43 (CN/China/-). 4 hits in the last 150 seconds
2019-08-14 02:30:32
186.147.237.51 attack
fail2ban
2019-08-14 02:47:12
5.134.79.89 attack
firewall-block, port(s): 23/tcp
2019-08-14 02:32:41

Recently Reported IPs

194.95.14.60 143.130.158.32 126.209.186.26 78.61.2.12
250.242.188.38 90.155.13.232 219.65.95.202 253.139.68.201
30.189.169.247 166.38.46.17 244.11.113.242 185.20.4.61
144.59.250.148 85.220.194.191 180.154.143.197 29.148.131.22
2a01:7e0:0:134::11ec 101.26.86.106 128.14.75.33 128.199.97.211