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: New Zealand

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

;; QUESTION SECTION:
;122.57.16.119.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 11:32:41 CST 2022
;; MSG SIZE  rcvd: 106
Host info
119.16.57.122.in-addr.arpa domain name pointer 122-57-16-119-adsl.sparkbb.co.nz.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
119.16.57.122.in-addr.arpa	name = 122-57-16-119-adsl.sparkbb.co.nz.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
52.175.53.45 attackbotsspam
Aug  4 10:55:41 vibhu-HP-Z238-Microtower-Workstation sshd\[2036\]: Invalid user giga from 52.175.53.45
Aug  4 10:55:41 vibhu-HP-Z238-Microtower-Workstation sshd\[2036\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.175.53.45
Aug  4 10:55:43 vibhu-HP-Z238-Microtower-Workstation sshd\[2036\]: Failed password for invalid user giga from 52.175.53.45 port 53358 ssh2
Aug  4 11:01:03 vibhu-HP-Z238-Microtower-Workstation sshd\[2232\]: Invalid user sandbox from 52.175.53.45
Aug  4 11:01:03 vibhu-HP-Z238-Microtower-Workstation sshd\[2232\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.175.53.45
...
2019-08-04 17:48:57
139.162.108.129 attackbotsspam
08/04/2019-00:39:28.037078 139.162.108.129 Protocol: 6 ET SCAN Suspicious inbound to mySQL port 3306
2019-08-04 17:18:57
31.208.65.235 attackspambots
Aug  4 03:57:57 www sshd\[41825\]: Invalid user johan from 31.208.65.235
Aug  4 03:57:57 www sshd\[41825\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.208.65.235
Aug  4 03:57:59 www sshd\[41825\]: Failed password for invalid user johan from 31.208.65.235 port 52144 ssh2
...
2019-08-04 18:10:38
92.119.160.181 attack
Port scan
2019-08-04 17:26:23
209.17.96.186 attackbotsspam
Port scan attempt detected by AWS-CCS, CTS, India
2019-08-04 17:51:17
35.190.193.42 attack
port scan and connect, tcp 22 (ssh)
2019-08-04 18:14:57
106.12.102.91 attackspambots
2019-08-04T04:55:47.001817abusebot-7.cloudsearch.cf sshd\[19505\]: Invalid user reza from 106.12.102.91 port 12348
2019-08-04 17:38:37
202.85.220.177 attackspambots
2019-08-04T04:48:49.397090abusebot-7.cloudsearch.cf sshd\[19490\]: Invalid user pin from 202.85.220.177 port 60080
2019-08-04 17:21:55
120.52.121.86 attackspambots
detected by Fail2Ban
2019-08-04 17:43:10
190.206.4.242 attackspambots
Unauthorised access (Aug  4) SRC=190.206.4.242 LEN=52 TTL=115 ID=28939 DF TCP DPT=445 WINDOW=8192 SYN
2019-08-04 17:37:06
202.51.74.92 attackbotsspam
xmlrpc attack
2019-08-04 17:39:30
104.248.49.171 attackspam
kp-sea2-01 recorded 2 login violations from 104.248.49.171 and was blocked at 2019-08-04 02:05:03. 104.248.49.171 has been blocked on 0 previous occasions. 104.248.49.171's first attempt was recorded at 2019-08-04 02:05:03
2019-08-04 18:23:57
179.184.217.83 attackbotsspam
Mar  8 02:56:57 motanud sshd\[19265\]: Invalid user jk from 179.184.217.83 port 41310
Mar  8 02:56:57 motanud sshd\[19265\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.184.217.83
Mar  8 02:57:00 motanud sshd\[19265\]: Failed password for invalid user jk from 179.184.217.83 port 41310 ssh2
2019-08-04 17:20:41
91.224.60.75 attack
Aug  4 02:41:22 * sshd[28118]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.224.60.75
Aug  4 02:41:23 * sshd[28118]: Failed password for invalid user stefan from 91.224.60.75 port 45126 ssh2
2019-08-04 17:46:48
199.195.248.177 attack
Aug  4 01:59:31 marvibiene sshd[34692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.248.177  user=root
Aug  4 01:59:33 marvibiene sshd[34692]: Failed password for root from 199.195.248.177 port 42088 ssh2
Aug  4 01:59:35 marvibiene sshd[34692]: Failed password for root from 199.195.248.177 port 42088 ssh2
Aug  4 01:59:31 marvibiene sshd[34692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.248.177  user=root
Aug  4 01:59:33 marvibiene sshd[34692]: Failed password for root from 199.195.248.177 port 42088 ssh2
Aug  4 01:59:35 marvibiene sshd[34692]: Failed password for root from 199.195.248.177 port 42088 ssh2
...
2019-08-04 17:52:55

Recently Reported IPs

122.6.11.232 122.54.133.239 122.6.170.199 122.6.198.81
122.6.199.190 122.6.198.72 122.6.201.69 122.6.201.60
122.6.202.19 122.6.202.252 122.6.202.248 122.6.226.35
122.6.227.87 122.9.205.254 122.6.227.239 122.96.31.102
122.9.179.88 122.96.28.150 122.96.34.68 123.118.7.199