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

;; QUESTION SECTION:
;116.222.117.142.		IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 20:04:47 CST 2025
;; MSG SIZE  rcvd: 108
Host info
142.117.222.116.in-addr.arpa domain name pointer 116-222-117-142.rev.home.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
142.117.222.116.in-addr.arpa	name = 116-222-117-142.rev.home.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
159.89.123.66 attackspam
Automatic report - XMLRPC Attack
2019-12-31 15:48:25
88.132.237.187 attackbotsspam
Dec 31 08:58:43 vmd17057 sshd\[4851\]: Invalid user temp from 88.132.237.187 port 58679
Dec 31 08:58:43 vmd17057 sshd\[4851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.132.237.187
Dec 31 08:58:46 vmd17057 sshd\[4851\]: Failed password for invalid user temp from 88.132.237.187 port 58679 ssh2
...
2019-12-31 16:03:16
162.211.109.201 attackbotsspam
Automatic report - XMLRPC Attack
2019-12-31 15:43:32
159.192.161.226 attackspambots
Port Scan
2019-12-31 16:01:48
103.36.101.161 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2019-12-31 15:59:35
113.254.250.232 attackspam
Port Scan
2019-12-31 15:41:25
222.186.175.148 attackbots
SSH Brute-Force reported by Fail2Ban
2019-12-31 15:50:23
159.203.201.233 attackbots
12/31/2019-07:27:33.658718 159.203.201.233 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-12-31 16:05:27
14.207.63.119 attackspam
19/12/31@01:27:53: FAIL: Alarm-Network address from=14.207.63.119
...
2019-12-31 15:52:59
85.111.53.103 attackbots
[portscan] Port scan
2019-12-31 15:56:53
45.141.84.25 attackbotsspam
Input Traffic from this IP, but critial abuseconfidencescore
2019-12-31 15:57:12
54.39.145.31 attack
2019-12-31T07:27:30.7827141240 sshd\[28592\]: Invalid user aoyule from 54.39.145.31 port 42748
2019-12-31T07:27:30.7865061240 sshd\[28592\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.145.31
2019-12-31T07:27:33.0334681240 sshd\[28592\]: Failed password for invalid user aoyule from 54.39.145.31 port 42748 ssh2
...
2019-12-31 16:08:08
119.120.40.40 attackbotsspam
CN from [119.120.40.40] port=5836 helo=aspmx.l.google.com
2019-12-31 16:12:48
185.175.93.9 attack
12/31/2019-08:32:08.353067 185.175.93.9 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-12-31 15:45:45
139.99.221.61 attack
Dec 31 03:27:37 ws19vmsma01 sshd[147604]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.221.61
Dec 31 03:27:39 ws19vmsma01 sshd[147604]: Failed password for invalid user liaan from 139.99.221.61 port 35512 ssh2
...
2019-12-31 16:00:05

Recently Reported IPs

89.93.108.243 160.101.228.221 44.3.212.189 212.120.193.204
220.40.11.213 244.40.210.168 163.27.113.142 148.53.27.234
125.31.118.245 55.79.213.84 67.25.35.13 3.107.13.177
89.18.243.6 178.28.239.236 201.68.90.244 20.225.253.224
59.89.159.97 9.174.193.222 255.73.211.167 139.135.192.219