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

;; QUESTION SECTION:
;114.145.122.139.		IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 28 02:08:00 CST 2025
;; MSG SIZE  rcvd: 108
Host info
139.122.145.114.in-addr.arpa domain name pointer p1715139-ipxg00c01niho.hiroshima.ocn.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.122.145.114.in-addr.arpa	name = p1715139-ipxg00c01niho.hiroshima.ocn.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
88.88.25.14 attackbots
Jan 15 22:00:35 ns382633 sshd\[8272\]: Invalid user augustine from 88.88.25.14 port 40268
Jan 15 22:00:35 ns382633 sshd\[8272\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.88.25.14
Jan 15 22:00:38 ns382633 sshd\[8272\]: Failed password for invalid user augustine from 88.88.25.14 port 40268 ssh2
Jan 15 22:48:24 ns382633 sshd\[16130\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.88.25.14  user=root
Jan 15 22:48:26 ns382633 sshd\[16130\]: Failed password for root from 88.88.25.14 port 40610 ssh2
2020-01-16 08:41:59
185.72.13.129 attackspam
Unauthorized connection attempt detected from IP address 185.72.13.129 to port 88 [J]
2020-01-16 08:34:26
178.242.56.217 attack
Unauthorized connection attempt detected from IP address 178.242.56.217 to port 4567 [J]
2020-01-16 08:34:45
177.185.159.95 attack
Unauthorized connection attempt detected from IP address 177.185.159.95 to port 80 [J]
2020-01-16 08:51:56
61.19.30.156 attackspam
Unauthorized connection attempt detected from IP address 61.19.30.156 to port 1433 [J]
2020-01-16 08:43:32
94.54.16.241 attackbotsspam
Unauthorized connection attempt detected from IP address 94.54.16.241 to port 5900 [J]
2020-01-16 08:41:07
221.13.12.45 attackbotsspam
Unauthorized connection attempt detected from IP address 221.13.12.45 to port 81 [T]
2020-01-16 08:29:53
37.187.30.114 attack
Unauthorized connection attempt detected from IP address 37.187.30.114 to port 8086 [J]
2020-01-16 08:26:19
124.198.115.226 attackbotsspam
Unauthorized connection attempt detected from IP address 124.198.115.226 to port 5555 [J]
2020-01-16 08:35:47
191.240.103.151 attackbots
Unauthorized connection attempt detected from IP address 191.240.103.151 to port 23 [J]
2020-01-16 08:47:45
188.113.86.23 attack
Unauthorized connection attempt detected from IP address 188.113.86.23 to port 23 [J]
2020-01-16 08:33:14
189.46.19.190 attackbotsspam
Unauthorized connection attempt detected from IP address 189.46.19.190 to port 80 [J]
2020-01-16 08:33:01
108.162.155.172 attack
Unauthorized connection attempt detected from IP address 108.162.155.172 to port 2220 [J]
2020-01-16 08:57:52
186.193.55.137 attackspambots
Unauthorized connection attempt detected from IP address 186.193.55.137 to port 85 [J]
2020-01-16 08:33:45
143.255.243.86 attackbotsspam
Unauthorized connection attempt detected from IP address 143.255.243.86 to port 80 [J]
2020-01-16 08:54:47

Recently Reported IPs

187.180.7.252 22.162.154.150 19.31.125.122 254.163.70.206
201.18.38.7 62.62.165.223 154.50.167.83 145.77.184.98
31.85.86.73 197.10.207.247 148.0.196.130 175.214.62.192
76.50.242.248 157.183.241.109 46.177.40.40 249.240.6.30
4.252.159.162 241.150.234.255 246.198.19.16 52.227.154.114