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

;; QUESTION SECTION:
;157.80.213.92.			IN	A

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

;; Query time: 75 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 11 03:48:49 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 92.213.80.157.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 92.213.80.157.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
202.14.122.154 attack
ENG,WP GET /wp-login.php
2019-10-26 03:19:16
202.166.211.181 attackbotsspam
Oct 25 15:00:57 server sshd\[24420\]: Invalid user supervisor from 202.166.211.181
Oct 25 15:00:57 server sshd\[24431\]: Invalid user supervisor from 202.166.211.181
Oct 25 15:00:58 server sshd\[24420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.166.211.181 
Oct 25 15:00:58 server sshd\[24431\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.166.211.181 
Oct 25 15:00:58 server sshd\[24455\]: Invalid user supervisor from 202.166.211.181
...
2019-10-26 03:02:05
123.185.8.207 attack
Automatic report - Port Scan Attack
2019-10-26 02:54:06
50.233.42.98 attackspambots
Sent mail to target address hacked/leaked from abandonia in 2016
2019-10-26 02:48:42
188.131.40.117 attackspam
Unauthorized connection attempt from IP address 188.131.40.117 on Port 445(SMB)
2019-10-26 03:15:07
198.27.116.229 attackbots
2019-10-25T18:16:50.480990Z 30fe15f372e5 New connection: 198.27.116.229:34006 (172.17.0.3:2222) [session: 30fe15f372e5]
2019-10-25T18:24:59.013791Z 72d647aa3acd New connection: 198.27.116.229:33620 (172.17.0.3:2222) [session: 72d647aa3acd]
2019-10-26 02:46:56
14.160.85.230 attackbots
Unauthorized connection attempt from IP address 14.160.85.230 on Port 445(SMB)
2019-10-26 02:44:05
91.223.246.89 attack
Unauthorized connection attempt from IP address 91.223.246.89 on Port 445(SMB)
2019-10-26 03:20:08
204.9.182.138 attackbots
Unauthorized connection attempt from IP address 204.9.182.138 on Port 445(SMB)
2019-10-26 03:10:03
60.246.0.72 attackspam
(imapd) Failed IMAP login from 60.246.0.72 (MO/Macao/nz0l72.bb60246.ctm.net): 1 in the last 3600 secs
2019-10-26 02:42:48
193.29.15.185 attackspam
Scanning random ports - tries to find possible vulnerable services
2019-10-26 03:20:43
206.189.239.123 attackspambots
Oct 23 06:27:01 mail sshd[30254]: Failed password for invalid user press from 206.189.239.123 port 33038 ssh2
Oct 23 06:27:01 mail sshd[30254]: Received disconnect from 206.189.239.123: 11: Bye Bye [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=206.189.239.123
2019-10-26 02:45:54
178.128.55.52 attackspam
Oct 25 19:44:37 XXX sshd[5119]: Invalid user ofsaa from 178.128.55.52 port 58794
2019-10-26 03:01:12
36.69.224.185 attackbots
Unauthorized connection attempt from IP address 36.69.224.185 on Port 445(SMB)
2019-10-26 02:59:06
179.162.94.58 attackbots
firewall-block, port(s): 23/tcp
2019-10-26 03:23:08

Recently Reported IPs

241.84.53.131 120.211.127.236 178.172.238.232 121.226.136.228
92.63.172.141 203.24.222.250 163.123.223.148 122.133.77.176
158.220.64.229 123.70.156.91 148.234.85.141 144.97.110.30
27.103.255.176 130.6.158.5 0.193.21.45 168.212.18.61
179.91.82.178 164.79.24.241 179.92.174.92 243.35.49.220