Skip to content

Hostname

tyan.com

Last fetched

tyan.com resolves to 113.196.154.133, announced in 113.196.128.0/19 by NCIC-TW - New Century InfoComm Tech Co., Ltd. in TW. tyan.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 · tyan.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/tyan.com

Resolution chain

IPv6 resolution

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

Attribution

new century infocomm

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
mitac international
Contact emails
nick.t@mitaccomputing.com, even.syao@mic.com.tw

Subdomains

Subdomain
antivirus.tyan.com
autodiscover.tyan.com
download.tyan.com
ftp.tyan.com
ftp1.tyan.com
giveaway.tyan.com
nextcloud.tyan.com
partner.tyan.com
wildcard.tyan.com
ww.tyan.com
www.tyan.com

Showing 11 of 11 subdomains (11 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-395.awsdns-49.com
  • ns47.worldnic.com
  • ns-1014.awsdns-62.net
  • 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
  • ns-1205.awsdns-22.org
  • ns-1551.awsdns-01.co.uk

MX records

  • hyspam.mic.com.tw
  • hyspam5.mic.com.tw

SPF policy

  • ip: 203.66.161.0/16
  • ip: 220.130.36.0/27
  • include: zcsend.net

Threat-feed evidence

History

Related pages

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