Skip to content

Hostname

xhctl.com.tw

Last fetched

xhctl.com.tw resolves to 160.16.222.57, announced in 160.16.128.0/17 by SAKURA-B - SAKURA Internet Inc. in JP. xhctl.com.tw 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 · xhctl.com.twRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint9.6/10canon.whisper.security/host/xhctl.com.tw

Resolution chain

IPv6 resolution

No AAAA record for xhctl.com.tw is recorded in WhisperGraph.

Attribution

sakura

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for xhctl.com.tw. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

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

  • anytld.apnic.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
  • ns1.xhctl.com.tw
  • ns2.xhctl.com.tw
  • h.dns.tw
  • a.twnic.net.tw
  • b.twnic.net.tw
  • c.twnic.net.tw
  • d.twnic.net.tw
  • e.twnic.net.tw
  • f.twnic.net.tw
  • g.twnic.net.tw
  • h.twnic.net.tw
  • ns1.coobi.work
  • ns2.coobi.work

MX records

  • mail.xhctl.com.tw

SPF policy

  • include: relay.mailchannels.net
  • a: xhctl.com.tw
  • mx: xhctl.com.tw

Threat-feed evidence

History

Related pages

Pivot from xhctl.com.tw 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: "xhctl.com.tw"})-[: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.