Skip to content

Hostname

vechain.com

Last fetched

vechain.com resolves to 108.128.177.100, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. vechain.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 · vechain.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/vechain.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of vechain.com owner
Contact emails
yuming@yinsibaohu.aliyun.com, george.yan@bitse.com, george.yan@vechain.com, 63884be6-3815-4dc9-884b-2fccf4205f59@identity-protect.org, 9544c26f-a521-47dc-abc0-60ca8e348b36@identity-protect.org

Subdomains

Subdomain
api.vechain.com
appagent.vechain.com
carbon.vechain.com
cdn.vechain.com
cronjob.vechain.com
jira.vechain.com
keyescrow.vechain.com
partner.vechain.com
platform.vechain.com
portal.vechain.com
summit.vechain.com
test.vechain.com

Showing 12 of 19. 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

  • ns-459.awsdns-57.com
  • ns-519.awsdns-00.net
  • ns-1481.awsdns-57.org
  • ns-1906.awsdns-46.co.uk

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 vechain.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: "vechain.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.