City: Fukuroi
Region: Sizuoka (Shizuoka)
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 '122.130.0.0 - 122.131.255.255'
% Abuse contact for '122.130.0.0 - 122.131.255.255' is 'hostmaster@nic.ad.jp'
inetnum: 122.130.0.0 - 122.131.255.255
netname: BIGLOBE
descr: BIGLOBE Inc.
descr: Higashi-shinagawa4-12-4
descr: Shinagawa-ku, Tokyo 140-0002, Japan
descr: 141-0032, JAPAN
country: JP
admin-c: JNIC1-AP
tech-c: JNIC1-AP
status: ALLOCATED PORTABLE
remarks: Email address for spam or abuse complaints : ip-admin@mesh.ad.jp
mnt-irt: IRT-JPNIC-JP
mnt-by: MAINT-JPNIC
mnt-lower: MAINT-JPNIC
last-modified: 2015-03-02T09:00: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 '122.130.0.0 - 122.130.255.255'
inetnum: 122.130.0.0 - 122.130.255.255
netname: BIGLOBE-14
descr: BIGLOBE Inc.
country: JP
admin-c: JP00020891
tech-c: JP00020891
last-modified: 2012-11-28T22: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-AU4); <<>> DiG 9.10.3-P4-Ubuntu <<>> 122.130.146.183
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7102
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;122.130.146.183. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026051601 1800 900 604800 86400
;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun May 17 04:54:55 CST 2026
;; MSG SIZE rcvd: 108183.146.130.122.in-addr.arpa domain name pointer flh3-122-130-146-183.osk.mesh.ad.jp.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
183.146.130.122.in-addr.arpa name = flh3-122-130-146-183.osk.mesh.ad.jp.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 188.254.0.124 | attackspambots | Invalid user server from 188.254.0.124 port 58016 |
2019-12-18 04:31:21 |
| 200.162.139.103 | attackspam | Unauthorized connection attempt detected from IP address 200.162.139.103 to port 445 |
2019-12-18 04:04:46 |
| 202.195.225.40 | attackbotsspam | 2019-12-17T16:41:38.897402abusebot-5.cloudsearch.cf sshd\[17654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.195.225.40 user=root 2019-12-17T16:41:41.052435abusebot-5.cloudsearch.cf sshd\[17654\]: Failed password for root from 202.195.225.40 port 38459 ssh2 2019-12-17T16:49:54.063454abusebot-5.cloudsearch.cf sshd\[17684\]: Invalid user zabbix from 202.195.225.40 port 35216 2019-12-17T16:49:54.068976abusebot-5.cloudsearch.cf sshd\[17684\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.195.225.40 |
2019-12-18 04:14:49 |
| 210.196.163.32 | attack | Dec 17 19:30:16 vps691689 sshd[12830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.196.163.32 Dec 17 19:30:18 vps691689 sshd[12830]: Failed password for invalid user guma from 210.196.163.32 port 2452 ssh2 Dec 17 19:36:05 vps691689 sshd[12985]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.196.163.32 ... |
2019-12-18 04:32:12 |
| 185.39.113.76 | attackspambots | Unauthorized connection attempt detected from IP address 185.39.113.76 to port 445 |
2019-12-18 04:25:49 |
| 40.92.20.74 | attackspam | Dec 17 19:14:05 debian-2gb-vpn-nbg1-1 kernel: [977611.749809] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=40.92.20.74 DST=78.46.192.101 LEN=52 TOS=0x02 PREC=0x00 TTL=106 ID=23497 DF PROTO=TCP SPT=13500 DPT=25 WINDOW=8192 RES=0x00 CWR ECE SYN URGP=0 |
2019-12-18 04:18:03 |
| 196.218.130.66 | attackbots | firewall-block, port(s): 23/tcp |
2019-12-18 04:32:29 |
| 203.177.1.108 | attack | Dec 17 15:20:46 ArkNodeAT sshd\[31339\]: Invalid user florina from 203.177.1.108 Dec 17 15:20:46 ArkNodeAT sshd\[31339\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.177.1.108 Dec 17 15:20:48 ArkNodeAT sshd\[31339\]: Failed password for invalid user florina from 203.177.1.108 port 53664 ssh2 |
2019-12-18 04:30:50 |
| 40.92.72.101 | attack | Dec 17 19:06:25 debian-2gb-vpn-nbg1-1 kernel: [977151.648398] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=40.92.72.101 DST=78.46.192.101 LEN=52 TOS=0x02 PREC=0x00 TTL=112 ID=21966 DF PROTO=TCP SPT=52311 DPT=25 WINDOW=8192 RES=0x00 CWR ECE SYN URGP=0 |
2019-12-18 04:00:15 |
| 198.44.15.175 | attackbotsspam | Dec 17 19:59:15 Ubuntu-1404-trusty-64-minimal sshd\[24214\]: Invalid user harald from 198.44.15.175 Dec 17 19:59:15 Ubuntu-1404-trusty-64-minimal sshd\[24214\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.44.15.175 Dec 17 19:59:16 Ubuntu-1404-trusty-64-minimal sshd\[24214\]: Failed password for invalid user harald from 198.44.15.175 port 49928 ssh2 Dec 17 20:08:50 Ubuntu-1404-trusty-64-minimal sshd\[2814\]: Invalid user zainuddin from 198.44.15.175 Dec 17 20:08:50 Ubuntu-1404-trusty-64-minimal sshd\[2814\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.44.15.175 |
2019-12-18 04:23:00 |
| 103.94.123.150 | attackbots | php WP PHPmyadamin ABUSE blocked for 12h |
2019-12-18 04:19:55 |
| 104.236.38.105 | attackbots | SSH login attempts. |
2019-12-18 04:28:02 |
| 81.10.64.184 | attackbots | Port 1433 Scan |
2019-12-18 04:06:01 |
| 92.119.160.67 | attackspam | Dec 17 21:18:51 debian-2gb-nbg1-2 kernel: \[266708.299289\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.67 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=53056 PROTO=TCP SPT=49164 DPT=4117 WINDOW=1024 RES=0x00 SYN URGP=0 |
2019-12-18 04:20:51 |
| 180.101.125.76 | attackspam | Dec 17 18:49:20 MK-Soft-Root2 sshd[26329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.125.76 Dec 17 18:49:22 MK-Soft-Root2 sshd[26329]: Failed password for invalid user wsh from 180.101.125.76 port 56468 ssh2 ... |
2019-12-18 04:05:34 |