Hostname
ledanji.com
Last fetched
ledanji.com resolves to 155.102.22.38, announced in 155.102.22.0/24 by Taobao - Zhejiang Taobao Network Co.,Ltd in KR. ledanji.com 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
- known-clean
Nutrition Label
Resolution chain
- 155.102.22.38
155.102.22.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · Seoul, KR
- 163.181.131.177
163.181.131.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · Frankfurt am Main, DE
- 163.181.131.188
163.181.131.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · Frankfurt am Main, DE
- 163.181.131.232
163.181.131.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · Frankfurt am Main, DE
- 163.181.131.233
163.181.131.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · Frankfurt am Main, DE
- 163.181.92.186
163.181.92.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · Frankfurt am Main, DE
- 163.181.131.231
163.181.131.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for ledanji.com is recorded in WhisperGraph.
Attribution
hangzhou alibaba advertising
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1599
- Registrant organisation
- net/ledanji.com net/ledanji.com
- Contact emails
- 2924940536@qq.com, laoyao3690@gmail.com
Subdomains
Showing 4 of 4 subdomains (4 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- fuji.ns.atrustdns.com
- michigan.ns.atrustdns.com
- 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 ledanji.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "ledanji.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.