City: unknown
Region: Tokyo
Country: Japan
Internet Service Provider: SoftBank
Hostname: unknown
Organization: unknown
Usage Type: unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '219.66.0.0 - 219.67.255.255'
% Abuse contact for '219.66.0.0 - 219.67.255.255' is 'hostmaster@nic.ad.jp'
inetnum: 219.66.0.0 - 219.67.255.255
netname: ULTINA
descr: SoftBank Corp.
descr: Tokyo Port City Takeshiba Office Tower, 1-7-1 Kaigan, Minato-ku, Tokyo, Japan
country: JP
admin-c: JNIC1-AP
tech-c: JNIC1-AP
status: ALLOCATED PORTABLE
remarks: Email address for spam or abuse complaints : net-abuse@odn.ad.jp
mnt-irt: IRT-JPNIC-JP
mnt-by: MAINT-JPNIC
mnt-lower: MAINT-JPNIC
last-modified: 2024-03-07T09:54:02Z
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 '219.66.128.0 - 219.66.255.255'
inetnum: 219.66.128.0 - 219.66.255.255
netname: ODN
descr: Open Data Network(JAPAN TELECOM CO.,LTD.)
country: JP
admin-c: JP00035900
tech-c: JP00035900
last-modified: 2008-07-15T02:17:06Z
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.34 (WHOIS-AU4); <<>> DiG 9.10.3-P4-Ubuntu <<>> 219.66.147.91
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49257
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;219.66.147.91. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025101500 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 15 18:10:44 CST 2025
;; MSG SIZE rcvd: 10691.147.66.219.in-addr.arpa domain name pointer MRIfx-103p13-91.ppp11.odn.ad.jp.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
91.147.66.219.in-addr.arpa name = MRIfx-103p13-91.ppp11.odn.ad.jp.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 212.47.238.207 | attackbotsspam | 2019-09-30T21:28:32.272923abusebot-4.cloudsearch.cf sshd\[8375\]: Invalid user git from 212.47.238.207 port 47388 |
2019-10-01 06:17:43 |
| 91.250.85.213 | attackbotsspam | Sep 30 11:27:34 php1 sshd\[24697\]: Invalid user test from 91.250.85.213 Sep 30 11:27:34 php1 sshd\[24697\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.250.85.213 Sep 30 11:27:35 php1 sshd\[24697\]: Failed password for invalid user test from 91.250.85.213 port 46626 ssh2 Sep 30 11:31:06 php1 sshd\[25001\]: Invalid user oy from 91.250.85.213 Sep 30 11:31:06 php1 sshd\[25001\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.250.85.213 |
2019-10-01 06:04:43 |
| 115.238.62.154 | attackbots | 2019-10-01T00:41:41.872460tmaserv sshd\[24799\]: Invalid user iy@123 from 115.238.62.154 port 18410 2019-10-01T00:41:41.879079tmaserv sshd\[24799\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.238.62.154 2019-10-01T00:41:43.748325tmaserv sshd\[24799\]: Failed password for invalid user iy@123 from 115.238.62.154 port 18410 ssh2 2019-10-01T00:45:31.203072tmaserv sshd\[24922\]: Invalid user sercon from 115.238.62.154 port 35856 2019-10-01T00:45:31.209365tmaserv sshd\[24922\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.238.62.154 2019-10-01T00:45:33.655467tmaserv sshd\[24922\]: Failed password for invalid user sercon from 115.238.62.154 port 35856 ssh2 ... |
2019-10-01 05:50:57 |
| 18.218.96.131 | attack | fail2ban honeypot |
2019-10-01 05:39:39 |
| 177.244.42.34 | attackspam | 2019-09-30T21:30:42.191628abusebot-3.cloudsearch.cf sshd\[27010\]: Invalid user sinus from 177.244.42.34 port 41200 |
2019-10-01 05:40:34 |
| 109.70.100.28 | attack | Automatic report - Banned IP Access |
2019-10-01 05:42:10 |
| 54.37.154.254 | attackbots | 2019-09-30T17:06:26.5419291495-001 sshd\[9643\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=254.ip-54-37-154.eu 2019-09-30T17:06:28.7277771495-001 sshd\[9643\]: Failed password for invalid user openfire from 54.37.154.254 port 47625 ssh2 2019-09-30T17:19:21.6394771495-001 sshd\[10601\]: Invalid user ubuntu from 54.37.154.254 port 40428 2019-09-30T17:19:21.6507861495-001 sshd\[10601\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=254.ip-54-37-154.eu 2019-09-30T17:19:23.3346731495-001 sshd\[10601\]: Failed password for invalid user ubuntu from 54.37.154.254 port 40428 ssh2 2019-09-30T17:22:41.4249041495-001 sshd\[10785\]: Invalid user ple from 54.37.154.254 port 59809 ... |
2019-10-01 05:37:17 |
| 54.37.226.173 | attackspam | Sep 30 23:55:12 SilenceServices sshd[578]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.226.173 Sep 30 23:55:13 SilenceServices sshd[578]: Failed password for invalid user mcadmin from 54.37.226.173 port 50064 ssh2 Sep 30 23:59:21 SilenceServices sshd[1696]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.226.173 |
2019-10-01 06:18:15 |
| 177.37.231.216 | attackspambots | SMB Server BruteForce Attack |
2019-10-01 06:09:45 |
| 49.88.112.66 | attackspam | Sep 30 22:58:44 v22018076622670303 sshd\[22883\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.66 user=root Sep 30 22:58:46 v22018076622670303 sshd\[22883\]: Failed password for root from 49.88.112.66 port 25854 ssh2 Sep 30 22:58:48 v22018076622670303 sshd\[22883\]: Failed password for root from 49.88.112.66 port 25854 ssh2 ... |
2019-10-01 05:59:11 |
| 40.77.167.80 | attack | Automatic report - Banned IP Access |
2019-10-01 06:08:46 |
| 112.21.191.244 | attackbotsspam | Sep 30 23:55:15 vps647732 sshd[21088]: Failed password for root from 112.21.191.244 port 41254 ssh2 Sep 30 23:59:01 vps647732 sshd[21124]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.21.191.244 ... |
2019-10-01 06:01:37 |
| 222.186.175.167 | attack | Sep 30 23:38:03 h2177944 sshd\[10804\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167 user=root Sep 30 23:38:05 h2177944 sshd\[10804\]: Failed password for root from 222.186.175.167 port 15744 ssh2 Sep 30 23:38:09 h2177944 sshd\[10804\]: Failed password for root from 222.186.175.167 port 15744 ssh2 Sep 30 23:38:14 h2177944 sshd\[10804\]: Failed password for root from 222.186.175.167 port 15744 ssh2 ... |
2019-10-01 05:42:54 |
| 178.209.106.178 | attack | Unauthorised access (Sep 30) SRC=178.209.106.178 LEN=40 TTL=244 ID=8658 DF TCP DPT=23 WINDOW=14600 SYN |
2019-10-01 06:10:35 |
| 212.47.251.164 | attackspambots | Oct 1 00:08:45 localhost sshd\[30708\]: Invalid user nx from 212.47.251.164 port 39732 Oct 1 00:08:45 localhost sshd\[30708\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.47.251.164 Oct 1 00:08:48 localhost sshd\[30708\]: Failed password for invalid user nx from 212.47.251.164 port 39732 ssh2 |
2019-10-01 06:19:20 |