城市(city): unknown
省份(region): unknown
国家(country): South Korea
运营商(isp): 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 '61.40.0.0 - 61.43.255.255'
% Abuse contact for '61.40.0.0 - 61.43.255.255' is 'irt@nic.or.kr'
inetnum: 61.40.0.0 - 61.43.255.255
netname: BORANET
descr: LG DACOM Corporation
admin-c: IM646-AP
tech-c: IM646-AP
country: KR
status: ALLOCATED PORTABLE
mnt-by: MNT-KRNIC-AP
mnt-irt: IRT-KRNIC-KR
last-modified: 2017-02-03T00:55:02Z
source: APNIC
irt: IRT-KRNIC-KR
address: 9, Jinheung-gil, Naju-si, Jeollanam-do
e-mail: irt@nic.or.kr
abuse-mailbox: irt@nic.or.kr
admin-c: IM574-AP
tech-c: IM574-AP
auth: # Filtered
remarks: irt@nic.or.kr was validated on 2020-04-09
mnt-by: MNT-KRNIC-AP
last-modified: 2025-09-04T01:00:01Z
source: APNIC
person: IP Manager
address: Seoul Yongsan-gu Hangang-daero 32
country: KR
phone: +82-2-1-01
e-mail: ipadm@lguplus.co.kr
nic-hdl: IM646-AP
mnt-by: MNT-KRNIC-AP
last-modified: 2021-10-05T05:20:03Z
source: APNIC
% Information related to '61.40.0.0 - 61.43.255.255'
inetnum: 61.40.0.0 - 61.43.255.255
netname: BORANET-KR
descr: LG DACOM Corporation
country: KR
admin-c: IA5-KR
tech-c: IA5-KR
status: ALLOCATED PORTABLE
mnt-by: MNT-KRNIC-AP
mnt-irt: IRT-KRNIC-KR
changed: hostmaster@nic.or.kr 20240912
remarks: This information has been partially mirrored by APNIC from
remarks: KRNIC. To obtain more specific information, please use the
remarks: KRNIC whois server at whois.kisa.or.kr.
source: KRNIC
person: IP Manager
address: Seoul Yongsan-gu Hangang-daero 32
address: LG UPLUS
country: KR
phone: +82-2-1-01
e-mail: ipadm@lguplus.co.kr
nic-hdl: IA5-KR
mnt-by: MNT-KRNIC-AP
changed: hostmaster@nic.or.kr 20240912
remarks: This information has been partially mirrored by APNIC from
remarks: KRNIC. To obtain more specific information, please use the
remarks: KRNIC whois server at whois.kisa.or.kr.
source: KRNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 61.43.12.34
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19880
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;61.43.12.34. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026060401 1800 900 604800 86400
;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jun 05 10:20:53 CST 2026
;; MSG SIZE rcvd: 104Host 34.12.43.61.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 34.12.43.61.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 114.67.110.126 | attackspambots | Jun 16 09:02:54 : SSH login attempts with invalid user |
2020-06-17 06:29:16 |
| 94.124.93.33 | attack | 1149. On Jun 16 2020 experienced a Brute Force SSH login attempt -> 4 unique times by 94.124.93.33. |
2020-06-17 06:34:48 |
| 222.186.180.223 | attack | 2020-06-16T22:29:47.683245shield sshd\[24048\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223 user=root 2020-06-16T22:29:49.704235shield sshd\[24048\]: Failed password for root from 222.186.180.223 port 33182 ssh2 2020-06-16T22:29:52.699649shield sshd\[24048\]: Failed password for root from 222.186.180.223 port 33182 ssh2 2020-06-16T22:29:56.107016shield sshd\[24048\]: Failed password for root from 222.186.180.223 port 33182 ssh2 2020-06-16T22:29:59.398749shield sshd\[24048\]: Failed password for root from 222.186.180.223 port 33182 ssh2 |
2020-06-17 06:33:33 |
| 20.43.15.149 | attack | Jun 16 22:47:04 debian-2gb-nbg1-2 kernel: \[14599125.481939\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=20.43.15.149 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=235 ID=54321 PROTO=TCP SPT=37723 DPT=22 WINDOW=65535 RES=0x00 SYN URGP=0 |
2020-06-17 06:18:16 |
| 46.197.1.66 | attackspam | 20/6/16@17:24:43: FAIL: Alarm-Network address from=46.197.1.66 20/6/16@17:24:44: FAIL: Alarm-Network address from=46.197.1.66 ... |
2020-06-17 06:23:27 |
| 154.8.196.30 | attackspam | SSH/22 MH Probe, BF, Hack - |
2020-06-17 06:15:20 |
| 88.102.244.211 | attackspambots | 21 attempts against mh-ssh on cloud |
2020-06-17 06:29:42 |
| 34.69.202.251 | attack | Jun 16 22:06:40 internal-server-tf sshd\[19776\]: Invalid user ansible from 34.69.202.251Jun 16 22:08:04 internal-server-tf sshd\[19819\]: Invalid user butter from 34.69.202.251 ... |
2020-06-17 06:10:41 |
| 79.106.4.202 | attackbotsspam | Autoban 79.106.4.202 ABORTED AUTH |
2020-06-17 06:35:01 |
| 110.45.244.102 | attack | Jun 16 13:43:00 dignus sshd[26538]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.45.244.102 Jun 16 13:43:02 dignus sshd[26538]: Failed password for invalid user admin from 110.45.244.102 port 58928 ssh2 Jun 16 13:46:49 dignus sshd[26815]: Invalid user sammy from 110.45.244.102 port 60151 Jun 16 13:46:49 dignus sshd[26815]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.45.244.102 Jun 16 13:46:50 dignus sshd[26815]: Failed password for invalid user sammy from 110.45.244.102 port 60151 ssh2 ... |
2020-06-17 06:31:21 |
| 89.223.94.93 | attackspambots | SSH Invalid Login |
2020-06-17 06:02:00 |
| 114.226.234.129 | attackbotsspam | port scan and connect, tcp 23 (telnet) |
2020-06-17 06:05:33 |
| 122.228.19.79 | attackbots | 122.228.19.79 was recorded 19 times by 5 hosts attempting to connect to the following ports: 43,3689,8088,8086,8123,8443,2525,82,3790,11300,1723,8800,40001,3460,4000,15000,7548. Incident counter (4h, 24h, all-time): 19, 161, 25716 |
2020-06-17 06:16:45 |
| 118.99.114.93 | attackspambots | DATE:2020-06-16 22:47:17, IP:118.99.114.93, PORT:5900 VNC brute force auth on honeypot server (epe-honey1-hq) |
2020-06-17 06:00:21 |
| 112.85.42.188 | attackspam | 06/16/2020-18:19:24.801844 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan |
2020-06-17 06:20:58 |