城市(city): unknown
省份(region): unknown
国家(country): Malaysia
运营商(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 '103.129.198.0 - 103.129.198.255'
% Abuse contact for '103.129.198.0 - 103.129.198.255' is 'abuse@wawahost.com.my'
inetnum: 103.129.198.0 - 103.129.198.255
netname: WAWAHOST-MY
descr: Westeros Communications (THAILAND) CO., LTD.
descr: https://ariskisp.com/rfc8805.csv
country: MY
geoloc: 3.1495654 101.7062673
admin-c: WTA1-AP
tech-c: WTA1-AP
abuse-c: AW1040-AP
status: ALLOCATED NON-PORTABLE
mnt-by: MAINT-WAWAHOST-MY
mnt-irt: IRT-WAWAHOST-MY
last-modified: 2026-03-02T13:16:56Z
source: APNIC
irt: IRT-WAWAHOST-MY
address: NO 60, JALAN KRUBONG HEIGHT 11,
address: TAMAN KRUBONG HEIGHT, 75250,
address: MELAKA, MALAYSIA.
e-mail: admin@wawahost.com.my
abuse-mailbox: abuse@wawahost.com.my
admin-c: WTA1-AP
tech-c: WTA1-AP
auth: # Filtered
remarks: admin@wawahost.com.my was validated on 2025-12-30
remarks: abuse@wawahost.com.my was validated on 2025-12-30
mnt-by: MAINT-WAWAHOST-MY
last-modified: 2025-12-30T13:11:54Z
source: APNIC
role: ABUSE WAWAHOSTMY
country: ZZ
address: NO 60, JALAN KRUBONG HEIGHT 11,
address: TAMAN KRUBONG HEIGHT, 75250,
address: MELAKA, MALAYSIA.
phone: +000000000
e-mail: admin@wawahost.com.my
admin-c: WTA1-AP
tech-c: WTA1-AP
nic-hdl: AW1040-AP
remarks: Generated from irt object IRT-WAWAHOST-MY
remarks: admin@wawahost.com.my was validated on 2025-12-30
remarks: abuse@wawahost.com.my was validated on 2025-12-30
abuse-mailbox: abuse@wawahost.com.my
mnt-by: APNIC-ABUSE
last-modified: 2025-12-30T13:12:23Z
source: APNIC
role: WAWAHOST TECHNOLOGY Administrator
address: NO 60, JALAN KRUBONG HEIGHT 11,
address: TAMAN KRUBONG HEIGHT, 75250,
address: MELAKA, MALAYSIA.
country: MY
phone: +60-105101111
e-mail: abuse@wawahost.com.my
admin-c: WTA1-AP
tech-c: WTA1-AP
nic-hdl: WTA1-AP
mnt-by: MAINT-WAWAHOST-MY
last-modified: 2024-10-03T16:20:04Z
remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
remarks: This IP address is being used by WAWAHOST's Customer
remarks: Please contact abuse@wawahost.com.my
remarks: For any abuse activity originated from this IP address
remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
source: APNIC
% Information related to '103.129.198.0/24AS215748'
route: 103.129.198.0/24
origin: AS215748
descr: LIGHT CLOUD - ROUTE OBJECT
mnt-by: MAINT-WAWAHOST-MY
last-modified: 2026-03-02T09:57:12Z
source: APNIC
% Information related to '103.129.198.0/24AS401783'
route: 103.129.198.0/24
origin: AS401783
descr: LIGHT CLOUD - ROUTE OBJECT
mnt-by: MAINT-WAWAHOST-MY
last-modified: 2026-03-02T09:56:52Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 103.129.198.137
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24575
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;103.129.198.137. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026042902 1800 900 604800 86400
;; Query time: 29 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 30 12:32:33 CST 2026
;; MSG SIZE rcvd: 108Host 137.198.129.103.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 137.198.129.103.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 190.85.108.186 | attack | Feb 2 19:17:22 MK-Soft-Root2 sshd[7612]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.108.186 Feb 2 19:17:24 MK-Soft-Root2 sshd[7612]: Failed password for invalid user testftp from 190.85.108.186 port 48552 ssh2 ... |
2020-02-03 03:34:04 |
| 179.61.164.248 | attackspam | (From eric@talkwithcustomer.com) Hey, You have a website nervedoc.org, right? Of course you do. I am looking at your website now. It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get. Not including all of the work you put into creating social media, videos, blog posts, emails, and so on. So you’re investing seriously in getting people to that site. But how’s it working? Great? Okay? Not so much? If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should. Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better. You could actually get up to 100X more conversions! I’m not making this up. As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes. He’s backed up by a study a |
2020-02-03 03:39:13 |
| 193.70.90.59 | attackbotsspam | Jul 21 07:10:30 ms-srv sshd[55222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.90.59 Jul 21 07:10:32 ms-srv sshd[55222]: Failed password for invalid user webaccess from 193.70.90.59 port 59074 ssh2 |
2020-02-03 03:21:03 |
| 114.43.151.229 | attackbotsspam | DATE:2020-02-02 16:07:30, IP:114.43.151.229, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc) |
2020-02-03 03:52:58 |
| 200.35.77.220 | attack | Unauthorized connection attempt detected from IP address 200.35.77.220 to port 5555 [J] |
2020-02-03 03:48:23 |
| 198.211.123.196 | attack | Unauthorized connection attempt detected from IP address 198.211.123.196 to port 2220 [J] |
2020-02-03 03:54:33 |
| 193.93.117.211 | attack | Oct 28 01:33:44 ms-srv sshd[7103]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.93.117.211 Oct 28 01:33:46 ms-srv sshd[7103]: Failed password for invalid user admin2 from 193.93.117.211 port 52105 ssh2 |
2020-02-03 03:14:49 |
| 193.70.8.163 | attackspambots | Aug 3 00:23:37 ms-srv sshd[37164]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.8.163 Aug 3 00:23:39 ms-srv sshd[37164]: Failed password for invalid user secure from 193.70.8.163 port 49268 ssh2 |
2020-02-03 03:28:09 |
| 193.36.119.53 | attack | Oct 1 16:43:18 ms-srv sshd[3922]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.36.119.53 Oct 1 16:43:20 ms-srv sshd[3922]: Failed password for invalid user uz from 193.36.119.53 port 60990 ssh2 |
2020-02-03 03:47:36 |
| 201.152.52.182 | attackbots | Honeypot attack, port: 445, PTR: dsl-201-152-52-182-dyn.prod-infinitum.com.mx. |
2020-02-03 03:17:04 |
| 193.252.192.149 | attack | Dec 6 11:40:47 ms-srv sshd[36027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.252.192.149 Dec 6 11:40:48 ms-srv sshd[36027]: Failed password for invalid user admin from 193.252.192.149 port 58452 ssh2 |
2020-02-03 03:55:00 |
| 49.88.112.113 | attack | Feb 2 09:51:28 wbs sshd\[934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.113 user=root Feb 2 09:51:29 wbs sshd\[934\]: Failed password for root from 49.88.112.113 port 12870 ssh2 Feb 2 09:53:18 wbs sshd\[949\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.113 user=root Feb 2 09:53:21 wbs sshd\[949\]: Failed password for root from 49.88.112.113 port 15347 ssh2 Feb 2 09:55:10 wbs sshd\[968\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.113 user=root |
2020-02-03 03:56:35 |
| 112.118.141.226 | attack | Honeypot attack, port: 5555, PTR: n112118141226.netvigator.com. |
2020-02-03 03:56:11 |
| 118.101.192.81 | attackspambots | Unauthorized connection attempt detected from IP address 118.101.192.81 to port 2220 [J] |
2020-02-03 03:39:34 |
| 193.77.225.17 | attack | Jan 15 22:38:42 ms-srv sshd[38928]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.77.225.17 Jan 15 22:38:44 ms-srv sshd[38928]: Failed password for invalid user nagios from 193.77.225.17 port 43940 ssh2 |
2020-02-03 03:18:21 |