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

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

;; QUESTION SECTION:
;122.193.247.20.			IN	A

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

;; Query time: 261 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 02:31:39 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 20.247.193.122.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 20.247.193.122.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.75.19.175 attackbots
Unauthorized connection attempt detected from IP address 51.75.19.175 to port 2220 [J]
2020-01-07 13:10:30
180.211.162.238 attackspam
Unauthorized connection attempt detected from IP address 180.211.162.238 to port 1433 [J]
2020-01-07 13:18:48
222.186.175.217 attackbots
Jan  7 04:58:10 hcbbdb sshd\[32415\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.217  user=root
Jan  7 04:58:11 hcbbdb sshd\[32415\]: Failed password for root from 222.186.175.217 port 15750 ssh2
Jan  7 04:58:28 hcbbdb sshd\[32445\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.217  user=root
Jan  7 04:58:30 hcbbdb sshd\[32445\]: Failed password for root from 222.186.175.217 port 50534 ssh2
Jan  7 04:58:47 hcbbdb sshd\[32445\]: Failed password for root from 222.186.175.217 port 50534 ssh2
2020-01-07 13:00:20
134.209.147.198 attack
Unauthorized connection attempt detected from IP address 134.209.147.198 to port 2220 [J]
2020-01-07 13:05:22
73.125.170.149 attack
Unauthorized connection attempt detected from IP address 73.125.170.149 to port 8000 [J]
2020-01-07 13:33:09
118.24.28.65 attackspambots
Unauthorized connection attempt detected from IP address 118.24.28.65 to port 2220 [J]
2020-01-07 13:07:32
41.38.50.147 attack
unauthorized connection attempt
2020-01-07 13:36:04
138.197.25.187 attackspam
Unauthorized connection attempt detected from IP address 138.197.25.187 to port 2220 [J]
2020-01-07 13:23:00
177.11.46.14 attackspambots
Unauthorized connection attempt detected from IP address 177.11.46.14 to port 4567 [J]
2020-01-07 13:03:20
58.217.18.16 attackbots
Unauthorized connection attempt detected from IP address 58.217.18.16 to port 23 [J]
2020-01-07 13:35:20
197.51.48.198 attackbotsspam
unauthorized connection attempt
2020-01-07 13:16:26
193.169.253.86 attackbotsspam
Unauthorized connection attempt detected from IP address 193.169.253.86 to port 8545 [J]
2020-01-07 13:02:01
188.190.217.81 attackspam
Unauthorized connection attempt detected from IP address 188.190.217.81 to port 23 [J]
2020-01-07 13:02:15
117.85.147.43 attackspam
Unauthorized connection attempt detected from IP address 117.85.147.43 to port 2323 [J]
2020-01-07 13:25:15
139.217.218.255 attackbots
Unauthorized connection attempt detected from IP address 139.217.218.255 to port 2220 [J]
2020-01-07 13:22:03

Recently Reported IPs

122.193.247.194 122.193.247.201 122.193.247.203 122.193.247.204
122.193.247.210 122.193.247.216 122.193.247.219 122.193.247.22
122.193.247.220 122.193.247.223 122.193.247.224 122.193.247.228
122.193.247.233 52.209.203.141 122.193.247.234 122.193.247.236
122.193.247.239 122.193.247.245 122.193.247.248 122.193.247.251