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

;; QUESTION SECTION:
;157.107.114.211.		IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Dec 13 03:33:52 CST 2024
;; MSG SIZE  rcvd: 108
Host info
211.114.107.157.in-addr.arpa domain name pointer ag114211.dynamic.ppp.asahi-net.or.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
211.114.107.157.in-addr.arpa	name = ag114211.dynamic.ppp.asahi-net.or.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.82.53.242 attack
Unauthorized connection attempt detected from IP address 222.82.53.242 to port 8443 [J]
2020-01-22 09:09:41
125.25.187.234 attack
20/1/21@23:56:35: FAIL: Alarm-Network address from=125.25.187.234
20/1/21@23:56:36: FAIL: Alarm-Network address from=125.25.187.234
...
2020-01-22 13:27:28
167.179.92.35 attack
" "
2020-01-22 13:05:52
125.24.78.100 attackspam
1579669017 - 01/22/2020 05:56:57 Host: 125.24.78.100/125.24.78.100 Port: 445 TCP Blocked
2020-01-22 13:15:17
95.167.225.81 attackbots
$f2bV_matches
2020-01-22 13:11:12
37.49.231.163 attack
Excessive Port-Scanning
2020-01-22 13:08:58
181.64.155.216 attackbots
Unauthorized connection attempt detected from IP address 181.64.155.216 to port 23 [J]
2020-01-22 09:13:48
178.219.16.226 attackbotsspam
Jan 22 01:49:12 ns382633 sshd\[23621\]: Invalid user user from 178.219.16.226 port 51704
Jan 22 01:49:12 ns382633 sshd\[23621\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.219.16.226
Jan 22 01:49:15 ns382633 sshd\[23621\]: Failed password for invalid user user from 178.219.16.226 port 51704 ssh2
Jan 22 02:12:26 ns382633 sshd\[27515\]: Invalid user chong from 178.219.16.226 port 39828
Jan 22 02:12:26 ns382633 sshd\[27515\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.219.16.226
2020-01-22 09:14:16
163.172.176.138 attackbots
Jan 22 05:45:33 server sshd[45520]: Failed password for invalid user tmp from 163.172.176.138 port 50262 ssh2
Jan 22 05:54:30 server sshd[45656]: Failed password for invalid user ubuntu from 163.172.176.138 port 52924 ssh2
Jan 22 05:56:53 server sshd[45697]: Failed password for invalid user alex from 163.172.176.138 port 51932 ssh2
2020-01-22 13:17:23
222.186.173.226 attackbotsspam
Unauthorized connection attempt detected from IP address 222.186.173.226 to port 22 [J]
2020-01-22 09:09:15
213.82.114.206 attackspam
SSH login attempts brute force.
2020-01-22 13:06:49
202.85.216.78 attack
Unauthorized connection attempt detected from IP address 202.85.216.78 to port 1433 [J]
2020-01-22 09:10:47
197.253.70.162 attackbots
Unauthorized connection attempt detected from IP address 197.253.70.162 to port 1433 [J]
2020-01-22 09:11:30
82.64.15.106 attack
Unauthorized connection attempt detected from IP address 82.64.15.106 to port 22 [J]
2020-01-22 09:03:50
190.83.134.101 attack
Unauthorized connection attempt detected from IP address 190.83.134.101 to port 23 [J]
2020-01-22 09:12:08

Recently Reported IPs

2.160.36.129 120.130.0.26 56.189.142.217 33.162.179.46
64.146.50.29 184.223.132.89 21.192.220.26 25.43.211.32
154.11.234.65 124.234.167.200 239.174.183.196 70.8.66.190
49.110.212.215 205.101.129.202 30.223.98.105 45.90.46.126
124.7.175.123 164.196.206.204 204.37.186.32 148.209.1.4