Hostname
danmu.com
Last fetched
danmu.com resolves to 112.84.131.73, announced in 112.80.0.0/13 by CHINA169-Backbone - CHINA UNICOM China169 Backbone in CN. danmu.com is listed by 1 threat feed; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONEListed by 1 threat feed. Advisory: score-zero-listing.
- Threat feeds listing this
- 1
- Verdict coverage
- listing-stopped
- First seen on a feed
- Thu, 19 Nov 2026 00:54:03 GMT
- Last seen on a feed
- Thu, 19 Nov 2026 04:56:01 GMT
Nutrition Label
Resolution chain
- 112.84.131.73
112.80.0.0/13 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1799962
- 113.59.44.64
113.59.0.0/17 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1809078
- 113.59.44.68
113.59.0.0/17 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1809078
- 116.153.78.151
116.153.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:8389504
- 116.153.78.164
116.153.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:8389504
- 116.162.169.12
116.162.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1816670
- 116.169.184.178
116.169.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:8389504
- 119.36.225.140
119.36.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1791247
- 122.193.250.189
122.192.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1799962
- 123.148.116.182
123.148.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1808926
- 123.6.33.135
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1784658
- 123.6.37.169
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1784658
- 123.6.40.102
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1784658
- 14.205.93.55
14.205.92.0/22 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 14.205.93.60
14.205.92.0/22 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 183.93.116.30
183.92.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:1791247
- 211.97.84.182
211.97.84.0/24 · UNICOM-GX-IDC - UNICOM Guangxi province network · geoname:1803300
- 220.197.201.183
220.197.192.0/19 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:8389504
- 36.249.93.214
36.248.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 36.249.95.93
36.248.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
IPv6 resolution
No AAAA record for danmu.com is recorded in WhisperGraph.
Attribution
cncgroup ip of shanghai idc
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1331
- Registrant organisation
- xiamen privacy protection service co.
- Contact emails
- fancymedia@163.com, hzy7yzez@enamewhois.com
Company
- Company
- danmu
Technology
danmu has been observed using 6 technologies somewhere in its estate. This is observed use, not an exposure finding.
- Nginx · web servers
- HTML5 Mobile Boilerplate · mobile application development platforms
- Baidu Analytics · analytics
- DNSPod · domain name services
- Tencent Exmail · email
- Tencent · content delivery network
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Sample outbound links
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for danmu.com.
DKIM signing
No DKIM signing vendor is attributed to danmu.com in WhisperGraph.
Nameservers
- ns1.qeodns.com
- ns2.qeodns.com
- f1g1ns1.dnspod.net
- f1g1ns2.dnspod.net
MX records
- mxbiz1.qq.com
- mxbiz2.qq.com
SPF policy
- include: spf.mail.qq.com
Threat-feed evidence
History
Related pages
Pivot from danmu.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.