Skip to content

Hostname

mail.edu.tw

Last fetched

mail.edu.tw resolves to 163.28.11.118, announced in 163.44.201.0/24 by ERX-TANET-ASN1 - Taiwan Academic Network (TANet) Information Center in TW. mail.edu.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 · mail.edu.twRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.8/10canon.whisper.security/host/mail.edu.tw

Resolution chain

IPv6 resolution

Attribution

erx tanet asn1 taiwan academic information center

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mail.edu.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 1 of 1 subdomain (1 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

  • 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
  • edudns-c1.edu.tw
  • edudns-c2.edu.tw
  • edudns-m1.edu.tw
  • edudns-r1.edu.tw
  • edudns-r2.edu.tw
  • moemoon.edu.tw
  • moestar.edu.tw

MX records

  • mg.edu.tw

SPF policy

  • ip: 163.28.10.0/23
  • ip: 163.28.127.0/24
  • ip: 163.28.52.0/24
  • ip: 163.28.84.0/24
  • ip: 2001:288:200:10::/63
  • ip: 2001:288:3100::/64
  • ip: 2001:288:5000:8::/64
  • ip: 2001:288:7100:127::/64

Threat-feed evidence

History

Related pages

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