Hostname
lingdong.cn
Last fetched
lingdong.cn resolves to 113.240.117.106, announced in 113.240.117.0/24 by CT-HuNan-Changsha-IDC - No.293,Wanbao Avenue in CN. lingdong.cn is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- unassessed
Nutrition Label
Resolution chain
- 113.240.117.106
113.240.117.0/24 · CT-HuNan-Changsha-IDC - No.293,Wanbao Avenue · geoname:8548599
- 113.240.117.108
113.240.117.0/24 · CT-HuNan-Changsha-IDC - No.293,Wanbao Avenue · geoname:8548599
- 115.223.9.113
115.223.8.0/21 · CHINATELECOM-ZHEJIANG-WENZHOU-IDC - WENZHOU, ZHEJIANG Province, P.R.China. · geoname:1791388
- 115.223.9.119
115.223.8.0/21 · CHINATELECOM-ZHEJIANG-WENZHOU-IDC - WENZHOU, ZHEJIANG Province, P.R.China. · geoname:1791388
- 116.153.39.131
116.153.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:8389504
- 116.153.39.133
116.153.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:8389504
- 121.22.232.167
121.16.0.0/13 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:2038087
- 121.22.232.168
121.16.0.0/13 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:2038087
- 121.22.232.170
121.16.0.0/13 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:2038087
- 218.11.0.26
218.11.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:2038087
- 218.11.0.75
218.11.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:2038087
- 218.11.0.76
218.11.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:2038087
- 36.41.168.165
36.41.168.0/21 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
- 36.41.168.170
36.41.168.0/21 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
- 36.41.168.171
36.41.168.0/21 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
- 36.42.77.164
36.42.72.0/21 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
- 36.42.77.165
36.42.72.0/21 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
- 36.42.77.167
36.42.72.0/21 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
- 116.153.39.136
116.153.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:8389504
- 116.153.39.134
116.153.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · geoname:8389504
IPv6 resolution
No AAAA record for lingdong.cn is recorded in WhisperGraph.
Attribution
cncgroup ip of shanghai idc
ORIGIN_AS
WHOIS identity
- Registrar
- registrar:阿里云计算有限公司(万网)
- Registrant organisation
- 南京零洞数智科技有限公司
- Contact emails
- wenzhuohao@lingdong.cn
Company
- Company
- Lingdong
Technology
Lingdong has been observed using 18 technologies somewhere in its estate. This is observed use, not an exposure finding.
- jQuery · javascript libraries
- Open Graph · content management system
- PHP · programming languages
- Nginx · web servers
- Amazon Web Services · cloud hosting
- Piwik PRO Core · consent management
- iCIMS · applicant tracking systems
- Element UI · javascript frameworks
- OpenResty · development
- Vue.js · javascript frameworks
- Node.js · programming languages
- Baidu Analytics · analytics
- Alibaba Cloud DNS · domain name services
- HiChina · cloud hosting
- Nuxt.js · javascript frameworks
- Tengine · load balancers
- Alibaba Cloud Object Storage Service · infrastructure as a service
- DedeCMS · content management system
Subdomains
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for lingdong.cn.
DKIM signing
No DKIM signing vendor is attributed to lingdong.cn in WhisperGraph.
Nameservers
- dns23.hichina.com
- dns24.hichina.com
MX records
- m1.feishu.cn
SPF policy
- include: _netblocks.m.feishu.cn
Threat-feed evidence
History
Related pages
Pivot from lingdong.cn 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.