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

;; QUESTION SECTION:
;122.193.244.134.		IN	A

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

;; Query time: 44 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 02:28:13 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 134.244.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 134.244.193.122.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
144.22.98.225 attackspam
Unauthorized connection attempt detected from IP address 144.22.98.225 to port 2220 [J]
2020-01-14 20:10:53
116.89.112.121 attackspam
Unauthorized connection attempt detected from IP address 116.89.112.121 to port 5555 [J]
2020-01-14 19:57:33
182.176.103.44 attackspambots
Jan 14 05:46:33 ns382633 sshd\[14044\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.176.103.44  user=root
Jan 14 05:46:35 ns382633 sshd\[14044\]: Failed password for root from 182.176.103.44 port 35216 ssh2
Jan 14 06:10:01 ns382633 sshd\[17564\]: Invalid user userftp from 182.176.103.44 port 60626
Jan 14 06:10:01 ns382633 sshd\[17564\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.176.103.44
Jan 14 06:10:03 ns382633 sshd\[17564\]: Failed password for invalid user userftp from 182.176.103.44 port 60626 ssh2
2020-01-14 20:21:40
200.29.108.214 attackspam
Unauthorized connection attempt detected from IP address 200.29.108.214 to port 2220 [J]
2020-01-14 20:34:52
119.145.27.92 attackspambots
Unauthorized connection attempt detected from IP address 119.145.27.92 to port 2220 [J]
2020-01-14 20:26:39
49.51.51.127 attackbotsspam
Unauthorized connection attempt detected from IP address 49.51.51.127 to port 8159 [J]
2020-01-14 20:16:55
116.252.0.28 attack
Unauthorized connection attempt detected from IP address 116.252.0.28 to port 8899 [J]
2020-01-14 20:27:22
159.203.193.244 attackbots
firewall-block, port(s): 39817/tcp
2020-01-14 20:23:12
197.51.3.111 attackspambots
Unauthorized connection attempt detected from IP address 197.51.3.111 to port 1433 [J]
2020-01-14 20:35:42
112.66.101.189 attackspam
Unauthorized connection attempt detected from IP address 112.66.101.189 to port 8080 [J]
2020-01-14 20:28:12
156.205.174.107 attack
Unauthorized connection attempt detected from IP address 156.205.174.107 to port 23 [J]
2020-01-14 20:23:33
112.232.238.96 attackspam
Unauthorized connection attempt detected from IP address 112.232.238.96 to port 80 [J]
2020-01-14 19:59:12
179.26.60.49 attack
Unauthorized connection attempt detected from IP address 179.26.60.49 to port 88
2020-01-14 20:22:57
185.189.103.31 attackspam
Unauthorized connection attempt detected from IP address 185.189.103.31 to port 8080 [J]
2020-01-14 20:21:13
93.46.97.40 attackspambots
Unauthorized connection attempt detected from IP address 93.46.97.40 to port 4567 [J]
2020-01-14 20:00:28

Recently Reported IPs

122.193.244.132 122.193.244.14 122.193.244.140 122.193.244.143
122.193.244.144 122.193.244.146 122.193.244.148 122.193.244.150
122.193.244.153 122.193.244.154 122.193.244.157 242.216.229.177
122.193.246.253 122.193.246.29 122.193.246.31 122.193.246.32
122.193.246.34 122.193.246.37 18.130.255.150 122.193.246.38