城市(city): Hitachi-Naka
省份(region): Ibaraki
国家(country): Japan
运营商(isp): KDDI Corporation
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '182.248.0.0 - 182.251.255.255'
% Abuse contact for '182.248.0.0 - 182.251.255.255' is 'hostmaster@nic.ad.jp'
inetnum: 182.248.0.0 - 182.251.255.255
netname: KDDI
descr: KDDI CORPORATION
descr: Garden Air Tower,3-10-10,Iidabashi,Chiyoda-ku,Tokyo,102-8460,Japan
country: JP
admin-c: JNIC1-AP
tech-c: JNIC1-AP
status: ALLOCATED PORTABLE
remarks: Email address for spam or abuse complaints : abuse@dion.ne.jp
mnt-by: MAINT-JPNIC
mnt-irt: IRT-JPNIC-JP
mnt-lower: MAINT-JPNIC
last-modified: 2024-04-17T02:59:33Z
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 '182.251.48.0 - 182.251.48.255'
inetnum: 182.251.48.0 - 182.251.48.255
netname: KDDI-NET
descr: KDDI CORPORATION
country: JP
admin-c: JP00000127
tech-c: JP00000181
last-modified: 2011-03-22T23:56:05Z
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 <<>> 182.251.48.124
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37729
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;182.251.48.124. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026012701 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 28 10:55:29 CST 2026
;; MSG SIZE rcvd: 107124.48.251.182.in-addr.arpa domain name pointer KD182251048124.au-net.ne.jp.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
124.48.251.182.in-addr.arpa name = KD182251048124.au-net.ne.jp.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 45.146.167.167 | attackbots | Repeated RDP login failures. Last user: Test |
2020-10-03 00:45:00 |
| 164.90.224.231 | attack | Oct 2 14:39:55 gospond sshd[31292]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.90.224.231 Oct 2 14:39:55 gospond sshd[31292]: Invalid user splunk from 164.90.224.231 port 51522 Oct 2 14:39:57 gospond sshd[31292]: Failed password for invalid user splunk from 164.90.224.231 port 51522 ssh2 ... |
2020-10-03 00:18:25 |
| 212.70.149.20 | attack | Oct 2 18:15:01 srv01 postfix/smtpd\[15589\]: warning: unknown\[212.70.149.20\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 18:15:03 srv01 postfix/smtpd\[12196\]: warning: unknown\[212.70.149.20\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 18:15:05 srv01 postfix/smtpd\[18918\]: warning: unknown\[212.70.149.20\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 18:15:07 srv01 postfix/smtpd\[16095\]: warning: unknown\[212.70.149.20\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 18:15:25 srv01 postfix/smtpd\[16854\]: warning: unknown\[212.70.149.20\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-10-03 00:18:01 |
| 167.99.204.168 | attackspam | Fail2Ban Ban Triggered |
2020-10-03 00:29:41 |
| 103.154.234.245 | attackspam | SCAN: Host Sweep CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found |
2020-10-03 00:29:10 |
| 142.93.235.47 | attackbots | Oct 2 09:26:13 NPSTNNYC01T sshd[6309]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.235.47 Oct 2 09:26:15 NPSTNNYC01T sshd[6309]: Failed password for invalid user teamspeak from 142.93.235.47 port 41724 ssh2 Oct 2 09:29:50 NPSTNNYC01T sshd[6423]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.235.47 ... |
2020-10-03 00:21:06 |
| 185.202.1.103 | attackspambots | Repeated RDP login failures. Last user: Administrator |
2020-10-03 00:41:34 |
| 192.241.235.192 | attack | MultiHost/MultiPort Probe, Scan, Hack - |
2020-10-03 00:21:48 |
| 212.70.149.83 | attackspambots | 2964 times SMTP brute-force |
2020-10-03 00:13:53 |
| 183.58.22.146 | attackbots | Repeated RDP login failures. Last user: Office |
2020-10-03 00:50:53 |
| 128.199.95.60 | attackbotsspam | Automatic Fail2ban report - Trying login SSH |
2020-10-03 00:23:59 |
| 174.138.40.185 | attack | SSH brute-force attempt |
2020-10-03 00:42:03 |
| 183.196.213.214 | attackspam | [N10.H2.VM2] Port Scanner Detected Blocked by UFW |
2020-10-03 00:23:33 |
| 140.143.30.217 | attackbots | Oct 1 20:22:09 xxxxxxx4 sshd[21904]: Invalid user stan from 140.143.30.217 port 60408 Oct 1 20:22:09 xxxxxxx4 sshd[21904]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.30.217 Oct 1 20:22:11 xxxxxxx4 sshd[21904]: Failed password for invalid user stan from 140.143.30.217 port 60408 ssh2 Oct 1 20:38:07 xxxxxxx4 sshd[23326]: Invalid user test1 from 140.143.30.217 port 39796 Oct 1 20:38:07 xxxxxxx4 sshd[23326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.30.217 Oct 1 20:38:08 xxxxxxx4 sshd[23326]: Failed password for invalid user test1 from 140.143.30.217 port 39796 ssh2 Oct 1 20:49:07 xxxxxxx4 sshd[24500]: Invalid user sinus from 140.143.30.217 port 48160 Oct 1 20:49:07 xxxxxxx4 sshd[24500]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.30.217 Oct 1 20:49:09 xxxxxxx4 sshd[24500]: Failed password for invalid user sin........ ------------------------------ |
2020-10-03 00:22:06 |
| 119.45.210.145 | attackbots | 2020-10-02T12:02:45.891971shield sshd\[29845\]: Invalid user musikbot from 119.45.210.145 port 57462 2020-10-02T12:02:45.900998shield sshd\[29845\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.45.210.145 2020-10-02T12:02:47.982898shield sshd\[29845\]: Failed password for invalid user musikbot from 119.45.210.145 port 57462 ssh2 2020-10-02T12:08:14.784701shield sshd\[30478\]: Invalid user dummy from 119.45.210.145 port 55212 2020-10-02T12:08:14.790009shield sshd\[30478\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.45.210.145 |
2020-10-03 00:48:34 |