119.28.100.147

Basic Info

City: Singapore

Region: unknown

Country: Singapore

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

IP	Type	Details	Datetime
119.28.100.67	attackbotsspam	[Wed Jun 10 08:08:02 2020] - DDoS Attack From IP: 119.28.100.67 Port: 32984	2020-07-16 21:47:11
119.28.100.67	attackspam	SmallBizIT.US 1 packets to tcp(7547)	2020-07-13 03:49:25
119.28.100.67	attackspambots	[Wed Jun 10 08:08:07 2020] - DDoS Attack From IP: 119.28.100.67 Port: 32984	2020-07-08 23:38:51
119.28.100.67	attackspam	Unauthorized connection attempt detected from IP address 119.28.100.67 to port 179 [J]	2020-03-01 05:39:31
119.28.100.67	attackspambots	Unauthorized connection attempt detected from IP address 119.28.100.67 to port 4155 [J]	2020-01-07 07:55:05
119.28.100.67	attack	" "	2019-11-30 15:51:00
119.28.100.67	attack	2715/tcp 1043/tcp 554/tcp... [2019-06-18/07-10]5pkt,5pt.(tcp)	2019-07-10 23:44:16

Whois info:

% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '119.28.96.0 - 119.28.123.255'

% Abuse contact for '119.28.96.0 - 119.28.123.255' is 'abuse@tencent.com'

inetnum:        119.28.96.0 - 119.28.123.255
netname:        TencentCloud
descr:          Tencent cloud computing (Beijing) Co., Ltd.
descr:          Floor 6, Yinke Building,38 Haidian St,
descr:          Haidian District Beijing
country:        SG
admin-c:        JT1125-AP
tech-c:         JX1747-AP
abuse-c:        AC1601-AP
status:         ALLOCATED NON-PORTABLE
mnt-by:         MAINT-CNNIC-AP
mnt-routes:     MAINT-TENCENT-NET-AP-CN
mnt-irt:        IRT-TencentCloud-CN
last-modified:  2022-03-01T02:19:06Z
source:         APNIC

irt:            IRT-TencentCloud-CN
address:        9F, FIYTA Building, Gaoxinnanyi Road, Southern
address:        District of Hi-tech Park, Shenzhen
e-mail:         tencent_noc@tencent.com
admin-c:        JT1125-AP
tech-c:         JX1747-AP
abuse-mailbox:  abuse@tencent.com
remarks:        abuse@tencent.com was validated on 2025-10-29
remarks:        tencent_noc@tencent.com was validated on 2025-10-29
auth:           # Filtered
mnt-by:         MAINT-CNNIC-AP
last-modified:  2025-11-18T00:34:40Z
source:         APNIC

role:           ABUSE CNNICCN
country:        ZZ
address:        Beijing, China
phone:          +000000000
e-mail:         ipas@cnnic.cn
admin-c:        IP50-AP
tech-c:         IP50-AP
nic-hdl:        AC1601-AP
remarks:        Generated from irt object IRT-CNNIC-CN
remarks:        ipas@cnnic.cn is invalid
abuse-mailbox:  ipas@cnnic.cn
mnt-by:         APNIC-ABUSE
last-modified:  2025-09-19T17:20:32Z
source:         APNIC

person:         James Tian
address:        9F, FIYTA Building, Gaoxinnanyi Road,Southern
address:        District of Hi-tech Park, Shenzhen
country:        CN
phone:          +86-755-86013388-84952
e-mail:         johnsonqu@tencent.com
nic-hdl:        JT1125-AP
mnt-by:         MAINT-CNNIC-AP
last-modified:  2024-03-19T08:21:31Z
source:         APNIC

person:         Jimmy Xiao
address:        9F, FIYTA Building, Gaoxinnanyi Road,Southern
address:        District of Hi-tech Park, Shenzhen
country:        CN
phone:          +86-755-86013388-80224
e-mail:         klayliang@tencent.com
nic-hdl:        JX1747-AP
mnt-by:         MAINT-CNNIC-AP
last-modified:  2021-09-17T00:38:09Z
source:         APNIC

% Information related to '119.28.96.0/20AS133478'

route:          119.28.96.0/20
descr:          ComsenzNet routes
origin:         AS133478
mnt-by:         MAINT-COMSENZ1-CN
last-modified:  2016-08-12T04:45:12Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4)

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.28.100.147
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43244
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;119.28.100.147.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 13 17:01:37 CST 2026
;; MSG SIZE  rcvd: 107

Host info

Host 147.100.28.119.in-addr.arpa. not found: 3(NXDOMAIN)

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 147.100.28.119.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
218.92.0.187	attack	Dec 4 13:26:36 ns381471 sshd[3535]: Failed password for root from 218.92.0.187 port 50776 ssh2 Dec 4 13:26:48 ns381471 sshd[3535]: error: maximum authentication attempts exceeded for root from 218.92.0.187 port 50776 ssh2 [preauth]	2019-12-04 20:27:12
165.22.186.9	attackspambots	DigitalOcean BotNet attack - 10s of requests to non-existent pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined, XSS attacks node-superagent/4.1.0	2019-12-04 20:58:56
54.37.154.113	attackspam	Dec 4 13:24:06 MK-Soft-Root2 sshd[10405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.154.113 Dec 4 13:24:08 MK-Soft-Root2 sshd[10405]: Failed password for invalid user bourrand from 54.37.154.113 port 35412 ssh2 ...	2019-12-04 20:44:54
91.204.188.50	attackbots	Dec 4 13:20:42 fr01 sshd[8429]: Invalid user admin from 91.204.188.50 Dec 4 13:20:42 fr01 sshd[8429]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.204.188.50 Dec 4 13:20:42 fr01 sshd[8429]: Invalid user admin from 91.204.188.50 Dec 4 13:20:44 fr01 sshd[8429]: Failed password for invalid user admin from 91.204.188.50 port 38726 ssh2 ...	2019-12-04 20:41:17
185.125.33.203	normal	This is not spam, it is a false-positive.	2019-12-04 20:27:18
14.162.216.5	attackspam	Dec 4 12:09:55 mail postfix/smtps/smtpd[19382]: warning: unknown[14.162.216.5]: SASL PLAIN authentication failed: Dec 4 12:19:06 mail postfix/smtpd[1699]: warning: unknown[14.162.216.5]: SASL PLAIN authentication failed: Dec 4 12:19:12 mail postfix/smtpd[2119]: warning: unknown[14.162.216.5]: SASL PLAIN authentication failed:	2019-12-04 20:51:52
150.95.110.90	attack	$f2bV_matches	2019-12-04 20:53:09
186.147.237.51	attackspambots	$f2bV_matches	2019-12-04 20:30:26
106.13.48.201	attackbots	pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.48.201 user=sshd Failed password for sshd from 106.13.48.201 port 53724 ssh2 Invalid user temp from 106.13.48.201 port 49934 pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.48.201 Failed password for invalid user temp from 106.13.48.201 port 49934 ssh2	2019-12-04 20:37:46
181.41.216.131	attackspam	Dec 4 13:37:32 relay postfix/smtpd\[20309\]: NOQUEUE: reject: RCPT from unknown\[181.41.216.131\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[181.41.216.131\]\> Dec 4 13:37:32 relay postfix/smtpd\[20309\]: NOQUEUE: reject: RCPT from unknown\[181.41.216.131\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[181.41.216.131\]\> Dec 4 13:37:32 relay postfix/smtpd\[20309\]: NOQUEUE: reject: RCPT from unknown\[181.41.216.131\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[181.41.216.131\]\> Dec 4 13:37:32 relay postfix/smtpd\[20309\]: NOQUEUE: reject: RCPT from unknown\[181.41.216.131\]: 554 5.7.1 \: Relay access denied\; from=\	2019-12-04 20:47:13
222.186.180.8	attackspambots	Dec 4 02:26:55 eddieflores sshd\[7179\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.8 user=root Dec 4 02:26:57 eddieflores sshd\[7179\]: Failed password for root from 222.186.180.8 port 1226 ssh2 Dec 4 02:27:12 eddieflores sshd\[7210\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.8 user=root Dec 4 02:27:15 eddieflores sshd\[7210\]: Failed password for root from 222.186.180.8 port 14074 ssh2 Dec 4 02:27:25 eddieflores sshd\[7210\]: Failed password for root from 222.186.180.8 port 14074 ssh2	2019-12-04 20:30:11
132.232.59.247	attack	Dec 4 03:41:04 home sshd[22339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.59.247 user=root Dec 4 03:41:06 home sshd[22339]: Failed password for root from 132.232.59.247 port 43334 ssh2 Dec 4 03:51:56 home sshd[22487]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.59.247 user=root Dec 4 03:51:58 home sshd[22487]: Failed password for root from 132.232.59.247 port 36140 ssh2 Dec 4 03:58:53 home sshd[22552]: Invalid user follina from 132.232.59.247 port 45624 Dec 4 03:58:53 home sshd[22552]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.59.247 Dec 4 03:58:53 home sshd[22552]: Invalid user follina from 132.232.59.247 port 45624 Dec 4 03:58:55 home sshd[22552]: Failed password for invalid user follina from 132.232.59.247 port 45624 ssh2 Dec 4 04:05:46 home sshd[22653]: Invalid user merlo from 132.232.59.247 port 55126 Dec 4 04:05:46 home sshd[22653]:	2019-12-04 20:36:54
217.182.170.81	attack	Dec 4 07:24:42 TORMINT sshd\[32057\]: Invalid user atlanta from 217.182.170.81 Dec 4 07:24:42 TORMINT sshd\[32057\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.170.81 Dec 4 07:24:44 TORMINT sshd\[32057\]: Failed password for invalid user atlanta from 217.182.170.81 port 35530 ssh2 ...	2019-12-04 20:52:22
185.125.33.203	normal	This is not spam, it is a false-positive.	2019-12-04 20:27:29
159.203.201.108	attack	[portscan] tcp/143 [IMAP] *(RWIN=65535)(12041142)	2019-12-04 20:47:30

Recently Reported IPs

20.168.6.41	31.169.82.68	57.141.16.97	35.208.217.108
202.144.137.94	110.78.153.121	2606:4700:10::6814:5318	2606:4700:10::6816:4140
20.221.68.74	10.223.24.110	134.35.157.43	2606:4700:10::6814:8420
2003:d6:a729:7200:81d8:b8be:f73d:9c8a	99.10.76.25	34.85.82.221	35.187.220.208
43.156.18.240	2606:4700:10::6814:6575	69.189.152.90	204.0.23.7