Hostname
hxcdl.com
Last fetched
hxcdl.com resolves to 134.122.187.34, announced in 134.122.187.0/24 by CTGSERVERLIMITED-AS-AP - CTG Server Limited in SG. hxcdl.com is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:55:42 GMT
- Last seen on a feed
- Mon, 12 Oct 2026 23:27:43 GMT
Nutrition Label
Resolution chain
- 134.122.187.34
134.122.187.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Singapore, SG
- 134.122.187.35
134.122.187.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Singapore, SG
- 134.122.187.36
134.122.187.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Singapore, SG
- 134.122.187.37
134.122.187.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Singapore, SG
- 156.234.231.103
156.234.231.0/24 · YANCYLIMITED-AS-HK - Yancy Limited · Hong Kong, HK
- 156.234.231.102
156.234.231.0/24 · YANCYLIMITED-AS-HK - Yancy Limited · Hong Kong, HK
- 156.234.231.105
156.234.231.0/24 · YANCYLIMITED-AS-HK - Yancy Limited · Hong Kong, HK
- 156.234.231.104
156.234.231.0/24 · YANCYLIMITED-AS-HK - Yancy Limited · Hong Kong, HK
- 156.234.231.107
156.234.231.0/24 · YANCYLIMITED-AS-HK - Yancy Limited · Hong Kong, HK
- 156.234.231.106
156.234.231.0/24 · YANCYLIMITED-AS-HK - Yancy Limited · Hong Kong, HK
- 156.234.231.108
156.234.231.0/24 · YANCYLIMITED-AS-HK - Yancy Limited · Hong Kong, HK
- 14.128.54.230
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
- 14.128.54.231
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
- 14.128.54.234
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
- 14.128.54.235
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
- 14.128.54.232
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
- 14.128.54.233
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
- 14.128.54.229
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
- 14.128.54.241
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
- 14.128.54.242
14.128.54.0/24 · CTGSERVERLIMITED-AS-AP - CTG Server Limited · Anyang-si, KR
IPv6 resolution
No AAAA record for hxcdl.com is recorded in WhisperGraph.
Attribution
ctgserverlimited ap ctg
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1923
- Registrant organisation
- bei jing shi hai xing chen dian li gong cheng you xian gong si
- Contact emails
- 1002231325@qq.com, 446017839@qq.com
Company
Technology
hxcdl.com has been observed using 1 technology somewhere in its estate. This is observed use, not an exposure finding.
- DNSPod · domain name services
Subdomains
| Subdomain |
|---|
| www.hxcdl.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for hxcdl.com.
DKIM signing
No DKIM signing vendor is attributed to hxcdl.com in WhisperGraph.
Nameservers
- a.dnspod.com
- b.dnspod.com
- c.dnspod.com
- ult01.dnspod.com
- ult02.dnspod.com
Threat-feed evidence
History
Related pages
Pivot from hxcdl.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.