Skip to content
Install MCP

Hostname

handletaiwan.com

Last fetched

handletaiwan.com resolves to 13.248.188.167, announced in 13.248.176.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. handletaiwan.com 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 · handletaiwan.comRouting diversity1.5/10Peering density9.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/handletaiwan.com

Resolution chain

IPv6 resolution

No AAAA record for handletaiwan.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:48
Registrant organisation
handle development co.,ltd.
Contact emails
anab8025@gmail.com, handletaiwan@gmail.com

Subdomains

Subdomain
en.handletaiwan.com
mail.handletaiwan.com
www.handletaiwan.com

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns-249.awsdns-31.com
  • ns-870.awsdns-44.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-1147.awsdns-15.org
  • ns-1711.awsdns-21.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • smtp.google.com

SPF policy

  • include: _spf.google.com
  • a: handletaiwan.com
  • mx: handletaiwan.com
  • include: _spf.ready-market.com
  • ip: 103.138.106.31

Threat-feed evidence

History

Related pages

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