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: Kamiseyachō

Region: Kanagawa

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 '27.132.9.0 - 27.132.175.255'

% Abuse contact for '27.132.9.0 - 27.132.175.255' is 'hostmaster@nic.ad.jp'

inetnum:        27.132.9.0 - 27.132.175.255
netname:        FBDC
descr:          FreeBit Co., Ltd.
descr:          13F E.Space Tower 3-6 Maruyama-cho,
descr:          Shibuya-ku,Tokyo,Japan
country:        JP
admin-c:        JNIC1-AP
tech-c:         JNIC1-AP
status:         ALLOCATED PORTABLE
remarks:        Email address for spam or abuse complaints : opinion@FreeBit.NET
mnt-by:         MAINT-JPNIC
mnt-irt:        IRT-JPNIC-JP
mnt-lower:      MAINT-JPNIC
last-modified:  2019-08-09T10:11:49Z
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

% Information related to '27.132.128.0 - 27.132.159.255'

inetnum:        27.132.128.0 - 27.132.159.255
netname:        FB-NET
descr:          FreeBit Co., Ltd.
country:        JP
admin-c:        JP00000154
tech-c:         JP00000154
last-modified:  2019-09-27T21:44:03Z
remarks:        This information has been partially mirrored by APNIC from
remarks:        JPNIC. To obtain more specific information, please use the
remarks:        JPNIC WHOIS Gateway at
remarks:        http://www.nic.ad.jp/en/db/whois/en-gateway.html or
remarks:        whois.nic.ad.jp for WHOIS client. (The WHOIS client
remarks:        defaults to Japanese output, use the /e switch for English
remarks:        output)
source:         JPNIC

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

;; QUESTION SECTION:
;27.132.150.26.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Aug 19 16:57:12 CST 2026
;; MSG SIZE  rcvd: 106
Host info
26.150.132.27.in-addr.arpa domain name pointer 26.150.132.27.ap.yournet.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
26.150.132.27.in-addr.arpa	name = 26.150.132.27.ap.yournet.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
125.124.253.134 attackbotsspam
Brute force attempt
2020-04-19 21:47:14
89.141.56.162 attackbots
bruteforce detected
2020-04-19 21:54:43
134.122.50.84 attackspam
2020-04-19T13:14:11.200382abusebot-5.cloudsearch.cf sshd[25786]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.50.84  user=root
2020-04-19T13:14:13.283464abusebot-5.cloudsearch.cf sshd[25786]: Failed password for root from 134.122.50.84 port 53250 ssh2
2020-04-19T13:14:13.477642abusebot-5.cloudsearch.cf sshd[25788]: Invalid user admin from 134.122.50.84 port 60304
2020-04-19T13:14:13.482974abusebot-5.cloudsearch.cf sshd[25788]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.50.84
2020-04-19T13:14:13.477642abusebot-5.cloudsearch.cf sshd[25788]: Invalid user admin from 134.122.50.84 port 60304
2020-04-19T13:14:15.174446abusebot-5.cloudsearch.cf sshd[25788]: Failed password for invalid user admin from 134.122.50.84 port 60304 ssh2
2020-04-19T13:14:15.367542abusebot-5.cloudsearch.cf sshd[25790]: Invalid user admin from 134.122.50.84 port 37706
...
2020-04-19 21:34:42
140.250.123.208 attack
postfix (unknown user, SPF fail or relay access denied)
2020-04-19 21:30:15
222.186.42.155 attackbotsspam
Apr 19 15:17:37 MainVPS sshd[846]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.155  user=root
Apr 19 15:17:39 MainVPS sshd[846]: Failed password for root from 222.186.42.155 port 13243 ssh2
Apr 19 15:17:42 MainVPS sshd[846]: Failed password for root from 222.186.42.155 port 13243 ssh2
Apr 19 15:17:37 MainVPS sshd[846]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.155  user=root
Apr 19 15:17:39 MainVPS sshd[846]: Failed password for root from 222.186.42.155 port 13243 ssh2
Apr 19 15:17:42 MainVPS sshd[846]: Failed password for root from 222.186.42.155 port 13243 ssh2
Apr 19 15:17:37 MainVPS sshd[846]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.155  user=root
Apr 19 15:17:39 MainVPS sshd[846]: Failed password for root from 222.186.42.155 port 13243 ssh2
Apr 19 15:17:42 MainVPS sshd[846]: Failed password for root from 222.186.42.155 port 13243 ssh2
A
2020-04-19 21:42:36
221.165.252.143 attack
$f2bV_matches
2020-04-19 21:26:50
51.255.197.164 attack
Apr 19 14:59:47 vpn01 sshd[30354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.197.164
Apr 19 14:59:48 vpn01 sshd[30354]: Failed password for invalid user pi from 51.255.197.164 port 44806 ssh2
...
2020-04-19 21:56:18
140.143.207.57 attackspambots
SSH Brute-Force. Ports scanning.
2020-04-19 21:41:12
222.190.130.62 attack
SSH Brute-Force reported by Fail2Ban
2020-04-19 21:37:07
198.98.52.100 attackbotsspam
SSHD unauthorised connection attempt (a)
2020-04-19 21:45:50
203.90.130.245 attackbotsspam
Port probing on unauthorized port 1433
2020-04-19 21:24:09
103.218.161.181 attackbotsspam
$f2bV_matches
2020-04-19 21:40:28
111.207.167.147 attackspambots
port scan and connect, tcp 1433 (ms-sql-s)
2020-04-19 22:09:52
192.241.185.193 attackspam
DigitalOcean BotNet attack - 10s of requests to non- pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined, XSS attacks
UA removed
2020-04-19 21:38:49
69.229.6.56 attackspambots
2020-04-19T14:19:38.316633ns386461 sshd\[4278\]: Invalid user server from 69.229.6.56 port 54582
2020-04-19T14:19:38.320985ns386461 sshd\[4278\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.229.6.56
2020-04-19T14:19:40.745433ns386461 sshd\[4278\]: Failed password for invalid user server from 69.229.6.56 port 54582 ssh2
2020-04-19T14:42:33.617031ns386461 sshd\[24410\]: Invalid user nr from 69.229.6.56 port 46478
2020-04-19T14:42:33.620985ns386461 sshd\[24410\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.229.6.56
...
2020-04-19 21:51:19

Recently Reported IPs

95.108.213.220 107.20.106.255 128.1.33.15 2606:4700:10::6814:4961
73.147.191.168 92.161.29.129 99.221.42.160 63.106.217.197
35.171.124.35 34.193.126.165 2606:4700:10::6814:5467 47.52.101.234
31.251.18.196 68.221.130.146 68.155.156.252 37.19.119.73
192.178.6.198 14.212.180.9 98.90.137.244 34.76.80.239