Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Kuala Lumpur

Region: Kuala Lumpur

Country: Malaysia

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '14.1.128.0 - 14.1.255.255'

% Abuse contact for '14.1.128.0 - 14.1.255.255' is 'network@ytlcomms.my'

inetnum:        14.1.128.0 - 14.1.255.255
netname:        YTLCOMMS-AS-AP
descr:          YTL Communications Sdn Bhd
descr:          8th Floor One Oriental Place
descr:          No 1, Jalan Hang Lekiu
country:        MY
org:            ORG-YCSB1-AP
admin-c:        YCSB1-AP
tech-c:         YCSB1-AP
abuse-c:        AY513-AP
status:         ALLOCATED PORTABLE
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-YTLCOMMS-MY
mnt-routes:     MAINT-YTLCOMMS-MY
mnt-irt:        IRT-YTLCOMMS-MY
last-modified:  2020-11-11T03:16:44Z
source:         APNIC

irt:            IRT-YTLCOMMS-MY
address:        8th Floor, One Oriental Place, No.1 Jalan Hang Lekiu, 50100 Kuala Lumpur.
e-mail:         network@ytlcomms.my
abuse-mailbox:  network@ytlcomms.my
admin-c:        YCSB1-AP
tech-c:         YCSB1-AP
auth:           # Filtered
remarks:        network@ytlcomms.my was validated on 2025-06-19
mnt-by:         MAINT-YTLCOMMS-MY
last-modified:  2025-09-04T05:45:48Z
source:         APNIC

organisation:   ORG-YCSB1-AP
org-name:       YTL Communications Sdn Bhd
org-type:       LIR
country:        MY
address:        18th Floor, Menara YTL
address:        205, Jalan Bukit Bintang,
phone:          +60187998888
e-mail:         cne@ytlcomms.my
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2023-09-05T02:15:36Z
source:         APNIC

role:           ABUSE YTLCOMMSMY
country:        ZZ
address:        8th Floor, One Oriental Place, No.1 Jalan Hang Lekiu, 50100 Kuala Lumpur.
phone:          +000000000
e-mail:         network@ytlcomms.my
admin-c:        YCSB1-AP
tech-c:         YCSB1-AP
nic-hdl:        AY513-AP
remarks:        Generated from irt object IRT-YTLCOMMS-MY
remarks:        network@ytlcomms.my was validated on 2025-06-19
abuse-mailbox:  network@ytlcomms.my
mnt-by:         APNIC-ABUSE
last-modified:  2025-06-19T07:08:52Z
source:         APNIC

role:           YTL COMMUNICATIONS SDN BHD - network administrator
address:        8th Floor, One Oriental Place, No.1 Jalan Hang Lekiu, 50100 Kuala Lumpur.
country:        MY
phone:          +603 2027 8888
fax-no:         +603 2027 8828
e-mail:         network@ytlcomms.my
admin-c:        YCSB1-AP
tech-c:         YCSB1-AP
nic-hdl:        YCSB1-AP
mnt-by:         MAINT-YTLCOMMS-MY
last-modified:  2009-11-03T23:57:11Z
source:         APNIC

% Information related to '14.1.128.0/18AS45960'

route:          14.1.128.0/18
descr:          YTL Communications
origin:         AS45960
mnt-by:         MAINT-YTLCOMMS-MY
last-modified:  2010-10-13T03:34:46Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.36-SNAPSHOT (WHOIS-AU5)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.1.150.118
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12111
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;14.1.150.118.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025110800 1800 900 604800 86400

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Nov 08 22:17:20 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 118.150.1.14.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 118.150.1.14.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
165.22.21.221 attackbots
Sep  4 15:29:02 SilenceServices sshd[12767]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.21.221
Sep  4 15:29:04 SilenceServices sshd[12767]: Failed password for invalid user joaquin from 165.22.21.221 port 33942 ssh2
Sep  4 15:33:30 SilenceServices sshd[14493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.21.221
2019-09-04 21:53:20
177.70.154.228 attack
445/tcp
[2019-09-04]1pkt
2019-09-04 21:57:45
159.89.207.210 attackbotsspam
Sep  4 15:06:53 minden010 sshd[731]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.207.210
Sep  4 15:06:55 minden010 sshd[731]: Failed password for invalid user gl from 159.89.207.210 port 38898 ssh2
Sep  4 15:11:31 minden010 sshd[5040]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.207.210
...
2019-09-04 21:49:58
51.91.249.178 attackbotsspam
Sep  4 16:08:10 server sshd\[32384\]: Invalid user image from 51.91.249.178 port 59032
Sep  4 16:08:10 server sshd\[32384\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.249.178
Sep  4 16:08:12 server sshd\[32384\]: Failed password for invalid user image from 51.91.249.178 port 59032 ssh2
Sep  4 16:11:53 server sshd\[5172\]: Invalid user db2fenc2 from 51.91.249.178 port 47196
Sep  4 16:11:53 server sshd\[5172\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.249.178
2019-09-04 21:19:44
115.94.204.156 attack
Sep  4 03:37:57 auw2 sshd\[4253\]: Invalid user ruthie from 115.94.204.156
Sep  4 03:37:57 auw2 sshd\[4253\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.94.204.156
Sep  4 03:38:00 auw2 sshd\[4253\]: Failed password for invalid user ruthie from 115.94.204.156 port 40812 ssh2
Sep  4 03:43:10 auw2 sshd\[4865\]: Invalid user harmless from 115.94.204.156
Sep  4 03:43:10 auw2 sshd\[4865\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.94.204.156
2019-09-04 21:46:39
18.27.197.252 attackspambots
Sep  4 15:34:20 lnxmail61 sshd[8156]: Failed password for root from 18.27.197.252 port 44160 ssh2
Sep  4 15:34:20 lnxmail61 sshd[8156]: Failed password for root from 18.27.197.252 port 44160 ssh2
2019-09-04 21:37:59
129.204.42.58 attack
Sep  4 03:03:54 lcdev sshd\[30530\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.42.58  user=root
Sep  4 03:03:55 lcdev sshd\[30530\]: Failed password for root from 129.204.42.58 port 41016 ssh2
Sep  4 03:11:47 lcdev sshd\[31369\]: Invalid user il from 129.204.42.58
Sep  4 03:11:47 lcdev sshd\[31369\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.42.58
Sep  4 03:11:50 lcdev sshd\[31369\]: Failed password for invalid user il from 129.204.42.58 port 60253 ssh2
2019-09-04 21:25:44
117.7.182.66 attackbots
34567/tcp
[2019-09-04]1pkt
2019-09-04 22:01:30
95.90.139.169 attackbots
Aug 31 09:52:32 itv-usvr-01 sshd[26493]: Invalid user a from 95.90.139.169
Aug 31 09:52:32 itv-usvr-01 sshd[26493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.90.139.169
Aug 31 09:52:32 itv-usvr-01 sshd[26493]: Invalid user a from 95.90.139.169
Aug 31 09:52:34 itv-usvr-01 sshd[26493]: Failed password for invalid user a from 95.90.139.169 port 49946 ssh2
Aug 31 09:59:11 itv-usvr-01 sshd[26735]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.90.139.169  user=root
Aug 31 09:59:12 itv-usvr-01 sshd[26735]: Failed password for root from 95.90.139.169 port 37650 ssh2
2019-09-04 22:06:29
23.129.64.200 attackbots
Sep  4 15:12:26 rotator sshd\[21453\]: Failed password for root from 23.129.64.200 port 13943 ssh2Sep  4 15:12:30 rotator sshd\[21453\]: Failed password for root from 23.129.64.200 port 13943 ssh2Sep  4 15:12:33 rotator sshd\[21453\]: Failed password for root from 23.129.64.200 port 13943 ssh2Sep  4 15:12:36 rotator sshd\[21453\]: Failed password for root from 23.129.64.200 port 13943 ssh2Sep  4 15:12:38 rotator sshd\[21453\]: Failed password for root from 23.129.64.200 port 13943 ssh2Sep  4 15:12:42 rotator sshd\[21453\]: Failed password for root from 23.129.64.200 port 13943 ssh2
...
2019-09-04 21:23:41
104.131.178.223 attack
Sep  4 15:35:31 plex sshd[990]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.178.223  user=root
Sep  4 15:35:33 plex sshd[990]: Failed password for root from 104.131.178.223 port 56700 ssh2
2019-09-04 21:48:26
23.129.64.168 attackbotsspam
Sep  4 15:44:02 vpn01 sshd\[26551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.168  user=root
Sep  4 15:44:04 vpn01 sshd\[26551\]: Failed password for root from 23.129.64.168 port 22053 ssh2
Sep  4 15:44:19 vpn01 sshd\[26551\]: Failed password for root from 23.129.64.168 port 22053 ssh2
2019-09-04 22:08:49
46.101.47.26 attack
WordPress login Brute force / Web App Attack on client site.
2019-09-04 21:43:19
119.235.48.202 attackspambots
TCP src-port=35447   dst-port=25    dnsbl-sorbs abuseat-org barracuda       (Project Honey Pot rated Suspicious)   (1046)
2019-09-04 21:44:23
144.217.161.22 attack
xmlrpc attack
2019-09-04 21:47:54

Recently Reported IPs

195.78.54.77 147.185.133.111 45.142.193.171 120.239.11.85
112.97.193.142 147.185.133.188 2001:1600:aaaf:102:f816:3eff:fe39:bd0 20.163.10.187
38.240.36.246 247.129.96.154 103.120.91.227 27.224.127.11
216.132.108.123 27.224.127.203 3.79.2.152 113.195.55.205
143.198.13.10 8.105.238.76 38.220.131.206 38.220.131.211