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

;; QUESTION SECTION:
;126.42.99.0.			IN	A

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

;; Query time: 72 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 21:04:59 CST 2025
;; MSG SIZE  rcvd: 104
Host info
0.99.42.126.in-addr.arpa domain name pointer softbank126042099000.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
0.99.42.126.in-addr.arpa	name = softbank126042099000.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.3.135.27 attackbots
Jan  8 20:05:21 ourumov-web sshd\[32084\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.3.135.27  user=games
Jan  8 20:05:24 ourumov-web sshd\[32084\]: Failed password for games from 106.3.135.27 port 37650 ssh2
Jan  8 20:12:14 ourumov-web sshd\[32562\]: Invalid user hduser from 106.3.135.27 port 56948
...
2020-01-09 03:31:32
60.8.4.130 attackspambots
Unauthorized connection attempt detected from IP address 60.8.4.130 to port 3389 [T]
2020-01-09 03:32:47
42.112.100.238 attackspambots
Telnet/23 MH Probe, BF, Hack -
2020-01-09 03:14:19
106.110.169.149 attackspam
Unauthorized connection attempt detected from IP address 106.110.169.149 to port 23 [T]
2020-01-09 03:09:00
42.117.170.193 attackbotsspam
Unauthorized connection attempt detected from IP address 42.117.170.193 to port 83 [T]
2020-01-09 03:36:14
176.104.128.210 attack
Unauthorized connection attempt detected from IP address 176.104.128.210 to port 21 [T]
2020-01-09 03:23:33
118.71.215.63 attackbots
Unauthorized connection attempt detected from IP address 118.71.215.63 to port 23 [T]
2020-01-09 03:04:34
164.52.24.178 attackbotsspam
Unauthorized connection attempt detected from IP address 164.52.24.178 to port 5001 [T]
2020-01-09 03:23:55
111.21.95.94 attackbots
Honeypot attack, port: 23, PTR: PTR record not found
2020-01-09 03:08:44
61.161.236.97 attack
Unauthorized connection attempt detected from IP address 61.161.236.97 to port 5555 [T]
2020-01-09 03:31:46
123.235.86.22 attackbotsspam
Unauthorized connection attempt detected from IP address 123.235.86.22 to port 23 [T]
2020-01-09 03:25:14
115.55.22.124 attack
Unauthorized connection attempt detected from IP address 115.55.22.124 to port 23 [T]
2020-01-09 03:06:02
106.87.89.102 attack
Unauthorized connection attempt detected from IP address 106.87.89.102 to port 22 [T]
2020-01-09 03:09:24
42.118.71.225 attackspam
Unauthorized connection attempt detected from IP address 42.118.71.225 to port 23 [T]
2020-01-09 03:12:53
106.53.72.119 attackspam
Unauthorized connection attempt detected from IP address 106.53.72.119 to port 22 [T]
2020-01-09 03:31:14

Recently Reported IPs

81.136.26.229 241.203.175.164 130.160.176.75 161.56.76.223
34.75.253.17 238.96.28.236 12.46.52.36 174.1.156.76
242.142.10.21 98.143.50.183 2.127.80.78 231.233.52.252
120.122.191.67 194.229.132.73 119.136.247.133 132.19.101.106
247.231.218.11 48.33.40.180 202.176.42.107 248.153.205.74