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

;; QUESTION SECTION:
;118.8.245.145.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 12 19:38:33 CST 2025
;; MSG SIZE  rcvd: 106
Host info
145.245.8.118.in-addr.arpa domain name pointer p2104146-ipoe.ipoe.ocn.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
145.245.8.118.in-addr.arpa	name = p2104146-ipoe.ipoe.ocn.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
171.243.41.184 attackspam
firewall-block, port(s): 8080/tcp
2019-06-29 18:28:46
41.216.186.87 attack
SASL Brute Force
2019-06-29 18:18:09
182.180.163.223 attackbotsspam
19/6/29@04:39:50: FAIL: Alarm-Intrusion address from=182.180.163.223
...
2019-06-29 18:39:40
195.128.158.1 attackspambots
[portscan] Port scan
2019-06-29 18:37:33
178.237.196.12 attack
[portscan] Port scan
2019-06-29 18:39:06
118.25.36.160 attackbots
Portscan or hack attempt detected by psad/fwsnort
2019-06-29 18:05:54
188.166.7.101 attackspambots
Invalid user jiang from 188.166.7.101 port 49292
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.7.101
Failed password for invalid user jiang from 188.166.7.101 port 49292 ssh2
Invalid user blackwave from 188.166.7.101 port 37472
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.7.101
2019-06-29 18:38:11
185.49.241.230 attackspambots
[portscan] Port scan
2019-06-29 18:32:44
37.139.12.160 attack
port scan and connect, tcp 8080 (http-proxy)
2019-06-29 18:17:04
162.144.110.32 attackbots
Sql/code injection probe
2019-06-29 18:23:07
110.77.216.178 attack
Jun 29 09:13:16 master sshd[23684]: Failed password for invalid user admin from 110.77.216.178 port 36805 ssh2
2019-06-29 18:14:24
167.99.186.116 attackbots
Automatic report - Web App Attack
2019-06-29 18:24:46
213.149.103.132 attackspambots
WordPress login Brute force / Web App Attack on client site.
2019-06-29 18:23:38
185.211.245.198 attack
Jun 29 11:03:07 mail postfix/smtpd\[9593\]: warning: unknown\[185.211.245.198\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 29 11:42:29 mail postfix/smtpd\[10493\]: warning: unknown\[185.211.245.198\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 29 11:42:38 mail postfix/smtpd\[10493\]: warning: unknown\[185.211.245.198\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 29 12:06:25 mail postfix/smtpd\[10858\]: warning: unknown\[185.211.245.198\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2019-06-29 18:19:23
152.136.83.180 attackspam
8088/tcp 6379/tcp 8080/tcp...
[2019-06-29]10pkt,9pt.(tcp)
2019-06-29 18:25:06

Recently Reported IPs

61.177.165.174 28.0.52.29 172.188.55.134 139.52.5.239
162.196.202.93 120.169.166.119 134.191.144.231 34.23.135.102
237.227.91.50 186.140.39.159 203.1.205.237 58.68.170.64
212.78.20.188 249.65.38.55 50.124.250.131 227.129.13.185
252.64.229.47 86.239.138.92 91.202.109.114 117.244.61.140