Skip to content

Hostname

ycloud.com

Last fetched

ycloud.com resolves to 155.102.51.1, announced in 155.102.77.0/24 by Taobao - Zhejiang Taobao Network Co.,Ltd in DE. ycloud.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · ycloud.comRouting diversity1.5/10Peering density8.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.0/10canon.whisper.security/host/ycloud.com

Resolution chain

IPv6 resolution

No AAAA record for ycloud.com is recorded in WhisperGraph.

Attribution

taobao zhejiang

ORIGIN_AS

WHOIS identity

Registrar
iana:1331
Registrant organisation
neo
Contact emails
lewdon@gmail.com

Subdomains

Subdomain
ai-cicd.ycloud.com
api-mx.ycloud.com
api-prepare.ycloud.com
api-test-ak.ycloud.com
api-test.ycloud.com
api.ycloud.com
attila-mock-server-test.ycloud.com
back-test.ycloud.com
callback-test.ycloud.com
callback.ycloud.com
cert-dev.ycloud.com
docs.ycloud.com

Showing 12 of 38. View all 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

Nameservers

  • ns3.dnsv4.com
  • ns4.dnsv4.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

MX records

  • mx1.feishu.cn
  • mx2.feishu.cn
  • mx3.feishu.cn

SPF policy

  • include: _netblocks.m.feishu.cn

Threat-feed evidence

History

Related pages

Pivot from ycloud.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: "ycloud.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.