Skip to content

Hostname

leaftech.tw

Last fetched

leaftech.tw resolves to 118.163.72.100, announced in 118.163.0.0/16 by HINET - Data Communication Business Group in TW. leaftech.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 · leaftech.twRouting diversity1.5/10Peering density7.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/leaftech.tw

Resolution chain

IPv6 resolution

No AAAA record for leaftech.tw is recorded in WhisperGraph.

Attribution

chunghwa

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for leaftech.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

Subdomain
118-163-72-100.leaftech.tw
118-163-72-158.leaftech.tw
118-163-72-159.leaftech.tw
118-163-72-160.leaftech.tw
118-163-72-97.leaftech.tw
210-60-106-221.leaftech.tw
210-60-106-222.leaftech.tw
211-75-138-31.leaftech.tw
bus-subsidy.leaftech.tw
eden.leaftech.tw
kbus.leaftech.tw

Showing 11 of 15. View all subdomains →

Mail and authentication

Nameservers

  • 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
  • 118-163-72-97.leaftech.tw
  • 210-60-106-221.leaftech.tw
  • 210-60-106-222.leaftech.tw
  • 211-75-138-31.leaftech.tw

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • 118-163-72-97.leaftech.tw

SPF policy

  • mx: leaftech.tw

Threat-feed evidence

History

Related pages

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