City: unknown
Region: unknown
Country: Japan
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '49.212.0.0 - 49.212.255.255'
% Abuse contact for '49.212.0.0 - 49.212.255.255' is 'hostmaster@nic.ad.jp'
inetnum: 49.212.0.0 - 49.212.255.255
netname: SAKURA-OSAKA
descr: SAKURA Internet Inc.
descr: GRAND GREEN OSAKA North, JAM BASE 3F, 6-38 Ofukacho, Kita-ku, Osaka-shi, Osaka 530-0011, Japan
admin-c: JNIC1-AP
tech-c: JNIC1-AP
remarks: Email address for spam or abuse complaints : abuse@sakura.ad.jp
country: JP
mnt-by: MAINT-JPNIC
mnt-lower: MAINT-JPNIC
mnt-irt: IRT-JPNIC-JP
status: ALLOCATED PORTABLE
last-modified: 2024-10-01T00:06:35Z
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 '49.212.174.0 - 49.212.174.255'
inetnum: 49.212.174.0 - 49.212.174.255
netname: SAKURA-NET
descr: SAKURA Internet Inc.
country: JP
admin-c: KT749JP
tech-c: JP00072233
last-modified: 2012-04-21T09:05:04Z
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.36-SNAPSHOT (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.212.174.16
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48939
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;49.212.174.16. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026042002 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Apr 21 11:25:25 CST 2026
;; MSG SIZE rcvd: 10616.174.212.49.in-addr.arpa domain name pointer os3-298-38512.vs.sakura.ne.jp.
b'16.174.212.49.in-addr.arpa name = os3-298-38512.vs.sakura.ne.jp.
Authoritative answers can be found from:
'| IP | Type | Details | Datetime |
|---|---|---|---|
| 45.119.84.18 | attack | WordPress login Brute force / Web App Attack on client site. |
2019-10-02 17:42:24 |
| 106.13.10.159 | attackspambots | k+ssh-bruteforce |
2019-10-02 17:52:44 |
| 109.111.74.132 | attackbotsspam | Brute force SMTP login attempts. |
2019-10-02 17:35:03 |
| 129.28.191.55 | attackbotsspam | Automatic report - Banned IP Access |
2019-10-02 17:41:50 |
| 192.227.136.68 | attack | 2019-10-02T09:23:18.094903shield sshd\[29046\]: Invalid user ubnt from 192.227.136.68 port 59386 2019-10-02T09:23:18.101323shield sshd\[29046\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.227.136.68 2019-10-02T09:23:20.371430shield sshd\[29046\]: Failed password for invalid user ubnt from 192.227.136.68 port 59386 ssh2 2019-10-02T09:27:56.634991shield sshd\[29247\]: Invalid user ubuntu from 192.227.136.68 port 46924 2019-10-02T09:27:56.640561shield sshd\[29247\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.227.136.68 |
2019-10-02 17:45:04 |
| 42.104.97.231 | attackspambots | Oct 2 09:01:23 root sshd[27554]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.104.97.231 Oct 2 09:01:24 root sshd[27554]: Failed password for invalid user minecraft from 42.104.97.231 port 11113 ssh2 Oct 2 09:06:17 root sshd[27634]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.104.97.231 ... |
2019-10-02 17:57:05 |
| 58.56.33.221 | attackbotsspam | $f2bV_matches |
2019-10-02 17:56:25 |
| 189.14.134.41 | attackspam | Oct 2 05:47:28 andromeda sshd\[29939\]: Invalid user pi from 189.14.134.41 port 36474 Oct 2 05:47:28 andromeda sshd\[29941\]: Invalid user pi from 189.14.134.41 port 36514 Oct 2 05:47:28 andromeda sshd\[29939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.14.134.41 |
2019-10-02 17:45:41 |
| 119.27.170.64 | attackbots | Oct 2 11:38:02 dedicated sshd[5680]: Invalid user ec2-user from 119.27.170.64 port 59666 |
2019-10-02 17:50:14 |
| 122.225.100.82 | attackbotsspam | Oct 2 01:16:54 plusreed sshd[12100]: Invalid user isaac from 122.225.100.82 ... |
2019-10-02 18:02:16 |
| 128.1.91.202 | attackspambots | 3389/tcp 6443/tcp 8443/tcp... [2019-08-29/10-02]7pkt,7pt.(tcp) |
2019-10-02 17:58:47 |
| 103.17.53.148 | attack | Oct 2 06:47:09 www5 sshd\[14106\]: Invalid user login from 103.17.53.148 Oct 2 06:47:09 www5 sshd\[14106\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.17.53.148 Oct 2 06:47:12 www5 sshd\[14106\]: Failed password for invalid user login from 103.17.53.148 port 40666 ssh2 ... |
2019-10-02 17:55:37 |
| 23.94.16.72 | attack | $f2bV_matches |
2019-10-02 18:04:19 |
| 49.234.5.134 | attackbots | Oct 2 12:29:13 hosting sshd[27937]: Invalid user vin from 49.234.5.134 port 36466 ... |
2019-10-02 17:49:53 |
| 40.89.159.174 | attackbots | Oct 2 07:04:25 ns41 sshd[30909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.89.159.174 |
2019-10-02 17:45:18 |