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:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '150.11.0.0 - 150.24.255.255'

% Abuse contact for '150.11.0.0 - 150.24.255.255' is 'hostmaster@nic.ad.jp'

inetnum:        150.11.0.0 - 150.24.255.255
netname:        JAPAN150
country:        JP
descr:          Japan Network Information Center
admin-c:        JNIC1-AP
tech-c:         JNIC1-AP
status:         ALLOCATED PORTABLE
notify:         hostmaster@nic.ad.jp
mnt-by:         MAINT-JPNIC
mnt-irt:        IRT-JPNIC-JP
last-modified:  2015-12-01T22:24:39Z
source:         APNIC

irt:            IRT-JPNIC-JP
address:        Uchikanda OS Bldg 4F, 2-12-6 Uchi-Kanda
address:        Chiyoda-ku, Tokyo 101-0047, japan
e-mail:         hostmaster@nic.ad.jp
abuse-mailbox:  hostmaster@nic.ad.jp
phone:          +81-3-5297-2311
fax-no:         +81-3-5297-2312
admin-c:        JNIC1-AP
tech-c:         JNIC1-AP
auth:           # Filtered
remarks:        hostmaster@nic.ad.jp was validated on 2024-11-27
mnt-by:         MAINT-JPNIC
last-modified:  2025-09-04T01:00:00Z
source:         APNIC

role:           Japan Network Information Center
address:        Uchikanda OS Bldg 4F, 2-12-6 Uchi-Kanda
address:        Chiyoda-ku, Tokyo 101-0047, Japan
country:        JP
phone:          +81-3-5297-2311
fax-no:         +81-3-5297-2312
e-mail:         hostmaster@nic.ad.jp
admin-c:        JI13-AP
tech-c:         JE53-AP
nic-hdl:        JNIC1-AP
mnt-by:         MAINT-JPNIC
last-modified:  2022-01-05T03:04:02Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.47 (WHOIS-AU4)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 150.17.158.213
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12614
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;150.17.158.213.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 22 11:32:12 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 213.158.17.150.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 213.158.17.150.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.230.7.76 attackbotsspam
Automatic report - Port Scan Attack
2019-11-07 21:52:44
46.151.151.211 attackspam
[portscan] Port scan
2019-11-07 21:59:34
180.76.36.226 attackbots
Invalid user info from 180.76.36.226 port 51176
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.36.226
Failed password for invalid user info from 180.76.36.226 port 51176 ssh2
Invalid user spring from 180.76.36.226 port 60796
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.36.226
2019-11-07 21:51:06
14.207.97.234 attackspambots
/xmlrpc.php
/wp-login.php
2019-11-07 21:23:58
188.75.80.159 attack
port scan and connect, tcp 1433 (ms-sql-s)
2019-11-07 21:35:03
154.85.39.58 attackspam
sshd jail - ssh hack attempt
2019-11-07 22:01:15
186.54.111.160 attack
firewall-block, port(s): 23/tcp
2019-11-07 21:36:13
219.134.115.114 attack
DATE:2019-11-07 07:19:47, IP:219.134.115.114, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2019-11-07 21:44:21
106.13.219.148 attackbotsspam
Nov  7 14:28:07 ns381471 sshd[14491]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.219.148
Nov  7 14:28:09 ns381471 sshd[14491]: Failed password for invalid user pawan from 106.13.219.148 port 59122 ssh2
2019-11-07 21:35:39
181.196.137.82 attackbotsspam
port scan and connect, tcp 23 (telnet)
2019-11-07 21:49:52
94.23.31.12 attackbots
2019-11-07T12:00:05.304695abusebot-2.cloudsearch.cf sshd\[2411\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns368159.ip-94-23-31.eu  user=bin
2019-11-07 21:39:54
81.22.45.73 attackbotsspam
2019-11-07T11:35:53.299522+01:00 lumpi kernel: [2945336.303932] INPUT:DROP:SPAMHAUS_EDROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.73 DST=172.31.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=37717 PROTO=TCP SPT=50202 DPT=59401 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-07 21:55:30
198.108.67.143 attackbotsspam
ET DROP Dshield Block Listed Source group 1 - port: 3389 proto: TCP cat: Misc Attack
2019-11-07 21:32:17
173.212.200.13 attackspam
Honeypot hit, critical abuseConfidenceScore, incoming Traffic from this IP
2019-11-07 21:39:09
46.10.161.57 attackspambots
Nov  7 08:43:06 ny01 sshd[15157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.10.161.57
Nov  7 08:43:08 ny01 sshd[15157]: Failed password for invalid user admin from 46.10.161.57 port 46126 ssh2
Nov  7 08:47:04 ny01 sshd[15584]: Failed password for root from 46.10.161.57 port 37011 ssh2
2019-11-07 21:53:03

Recently Reported IPs

213.91.251.124 120.246.224.254 0.220.4.101 180.164.66.64
10.111.35.16 2a02:4780:bad:12:fced:1ff:fe12:395 126.113.87.151 121.234.219.140
2606:4700:10::6814:9603 2606:4700:10::6814:8954 2606:4700:10::6816:682 2606:4700:10::6816:4832
2606:4700:10::ac43:2938 2606:4700:10::6814:6934 2606:4700:10::6814:9156 2606:4700:10::6814:5569
35.255.65.61 106.28.185.127 112.13.112.154 134.245.50.77