Hostname
xd0g.com
Last fetched
xd0g.com resolves to 101.72.227.199, announced in 101.72.0.0/14 by CHINA169-Backbone - CHINA UNICOM China169 Backbone in CN. xd0g.com is listed by 2 threat feeds; reconciled level CRITICAL.
Threat posture
60threat score (procedure-native scale)
CRITICALListed by 2 threat feeds. At least one source recommends blocking.
Categories: Command-and-control
- Threat feeds listing this
- 2
- 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
- 101.72.227.199
101.72.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 114.132.171.157
114.132.128.0/18 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Guangzhou, CN
- 116.162.169.140
116.162.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Changsha, CN
- 116.162.169.143
116.162.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Changsha, CN
- 116.169.184.51
116.169.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 119.36.225.136
119.36.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Wuhan, CN
- 119.36.225.186
119.36.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Wuhan, CN
- 123.6.33.110
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 123.6.40.137
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 123.6.40.192
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 123.6.42.83
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 14.205.93.52
14.205.92.0/22 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Dali, CN
- 211.97.84.78
211.97.84.0/24 · UNICOM-GX-IDC - UNICOM Guangxi province network
- 220.197.201.187
220.197.192.0/19 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 220.197.201.194
220.197.192.0/19 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 36.249.93.83
36.248.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Xiamen, CN
- 36.249.93.85
36.248.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Xiamen, CN
- 58.144.195.188
58.144.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Chongqing, CN
- 60.28.220.101
60.28.0.0/15 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 60.28.220.71
60.28.0.0/15 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
IPv6 resolution
No AAAA record for xd0g.com is recorded in WhisperGraph.
Attribution
shenzhen tencent computer
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1697
Subdomains
| Subdomain |
|---|
| bi.xd0g.com |
| fyht.xd0g.com |
| zj.xd0g.com |
Showing 3 of 4. View all subdomains →
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for xd0g.com.
DKIM signing
No DKIM signing vendor is attributed to xd0g.com in WhisperGraph.
Nameservers
- ns1.qeodns.com
- ns2.qeodns.com
- jazz.dnspod.net
- pianist.dnspod.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
Threat-feed evidence
History
Related pages
Pivot from xd0g.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.