Skip to content

Hostname

ebc.net.tw

Last fetched

ebc.net.tw resolves to 13.227.192.103, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. ebc.net.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 · ebc.net.twRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/ebc.net.tw

Resolution chain

IPv6 resolution

No AAAA record for ebc.net.tw is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
????????????
Contact emails
carrie_chung@ebc.net.tw, legal_public@ebc.net.tw

Subdomains

Subdomain
ai-agent.ebc.net.tw
ai-star.ebc.net.tw
asia.ebc.net.tw
blog.ebc.net.tw
drama.ebc.net.tw
e-club.ebc.net.tw
ebc-oos1.ebc.net.tw
eflow.ebc.net.tw
emovie.ebc.net.tw
etmovie.ebc.net.tw
ettv.ebc.net.tw
ettvasia.ebc.net.tw

Showing 12 of 52. 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-360.awsdns-45.com
  • ns-917.awsdns-50.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-1080.awsdns-07.org
  • ns-1770.awsdns-29.co.uk

MX records

  • ebc-net-tw.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • ip: 220.229.241.80
  • ip: 220.229.241.81
  • ip: 61.219.52.123
  • ip: 61.219.52.124

Threat-feed evidence

History

Related pages

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