Skip to content

Hostname

hle.com.tw

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

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

Subdomain
accounts.hle.com.tw
api.hle.com.tw
app.hle.com.tw
cdn.hle.com.tw
edisc.hle.com.tw
edisc3.hle.com.tw
een-repo.hle.com.tw
ena-news-search.hle.com.tw
eventprotect.hle.com.tw
git.hle.com.tw
h5.hle.com.tw
hanlindigi.hle.com.tw

Showing 12 of 35. 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-182.awsdns-22.com
  • ns-911.awsdns-49.net
  • ns-1146.awsdns-15.org
  • ns-1857.awsdns-40.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com
  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Threat-feed evidence

History

Related pages

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