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

;; QUESTION SECTION:
;122.21.238.242.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 00:11:55 CST 2022
;; MSG SIZE  rcvd: 107
Host info
242.238.21.122.in-addr.arpa domain name pointer p4530242-ipngn25601marunouchi.tokyo.ocn.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
242.238.21.122.in-addr.arpa	name = p4530242-ipngn25601marunouchi.tokyo.ocn.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
139.189.199.7 attackbotsspam
GPON Home Routers Remote Code Execution Vulnerability CVE 2018-10562, PTR: PTR record not found
2020-02-08 03:49:19
103.250.186.78 attackbotsspam
Microsoft SQL Server User Authentication Brute Force Attempt, PTR: PTR record not found
2020-02-08 03:58:00
152.32.170.248 attackspam
fraudulent SSH attempt
2020-02-08 03:56:11
211.72.15.95 attackspambots
Unauthorized connection attempt from IP address 211.72.15.95 on Port 445(SMB)
2020-02-08 03:43:28
178.151.245.46 attack
Unauthorized connection attempt from IP address 178.151.245.46 on Port 445(SMB)
2020-02-08 03:53:08
138.197.138.67 attack
Automatic report - SSH Brute-Force Attack
2020-02-08 03:35:56
183.83.236.251 attack
Feb  7 12:36:28 db01 sshd[9976]: Did not receive identification string from 183.83.236.251
Feb  7 12:36:29 db01 sshd[9977]: reveeclipse mapping checking getaddrinfo for broadband.actcorp.in [183.83.236.251] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  7 12:36:30 db01 sshd[9977]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.83.236.251  user=r.r
Feb  7 12:36:31 db01 sshd[9977]: Failed password for r.r from 183.83.236.251 port 12044 ssh2
Feb  7 12:36:31 db01 sshd[9977]: Connection closed by 183.83.236.251 [preauth]
Feb  7 12:36:33 db01 sshd[9989]: reveeclipse mapping checking getaddrinfo for broadband.actcorp.in [183.83.236.251] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  7 12:36:33 db01 sshd[9989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.83.236.251  user=r.r
Feb  7 12:36:35 db01 sshd[9989]: Failed password for r.r from 183.83.236.251 port 11828 ssh2
Feb  7 12:37:03 db01 sshd[9989]:........
-------------------------------
2020-02-08 03:54:18
185.57.249.189 attack
Unauthorized connection attempt from IP address 185.57.249.189 on Port 445(SMB)
2020-02-08 03:38:37
177.75.69.16 attackspam
Unauthorized connection attempt from IP address 177.75.69.16 on Port 445(SMB)
2020-02-08 03:49:01
185.18.7.105 attackspambots
Unauthorized connection attempt from IP address 185.18.7.105 on Port 445(SMB)
2020-02-08 04:13:34
156.236.119.165 attack
Feb  7 07:17:49 auw2 sshd\[19842\]: Invalid user eey from 156.236.119.165
Feb  7 07:17:49 auw2 sshd\[19842\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=156.236.119.165
Feb  7 07:17:51 auw2 sshd\[19842\]: Failed password for invalid user eey from 156.236.119.165 port 43690 ssh2
Feb  7 07:23:43 auw2 sshd\[20525\]: Invalid user wqd from 156.236.119.165
Feb  7 07:23:43 auw2 sshd\[20525\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=156.236.119.165
2020-02-08 03:37:52
90.57.231.68 attackbotsspam
2020-02-07T13:38:32.831560vostok sshd\[27435\]: Invalid user zft from 90.57.231.68 port 30110 | Triggered by Fail2Ban at Vostok web server
2020-02-08 04:15:02
179.184.8.142 attackbotsspam
$f2bV_matches
2020-02-08 03:44:09
154.126.56.85 attack
Failed password for root from 154.126.56.85 port 37488 ssh2
2020-02-08 03:40:12
50.100.110.92 attack
Feb  7 14:46:16 server sshd[7806]: Failed password for invalid user ztr from 50.100.110.92 port 56150 ssh2
Feb  7 15:01:59 server sshd[7980]: Failed password for invalid user zss from 50.100.110.92 port 35880 ssh2
Feb  7 15:04:49 server sshd[7995]: Failed password for invalid user sbt from 50.100.110.92 port 36980 ssh2
2020-02-08 04:10:48

Recently Reported IPs

59.152.104.229 27.6.206.155 39.50.26.151 187.176.6.250
220.180.157.29 116.85.6.115 183.89.166.185 37.19.72.239
45.83.66.151 41.188.46.123 188.48.82.62 83.216.185.77
212.119.215.182 178.213.133.231 201.156.122.19 190.188.213.95
24.240.108.14 27.199.64.41 184.90.136.82 200.159.114.115