Skip to content

Hostname

timo.vn

Last fetched

timo.vn resolves to 13.215.64.52, announced in 13.214.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SG. timo.vn 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 · timo.vnRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint6.0/10canon.whisper.security/host/timo.vn

Resolution chain

IPv6 resolution

No AAAA record for timo.vn is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

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

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

  • ns-260.awsdns-32.com
  • ns-964.awsdns-56.net
  • nsbak.pavietnam.net
  • ns-1351.awsdns-40.org
  • ns-2022.awsdns-60.co.uk
  • ns1.pavietnam.vn
  • ns2.pavietnam.vn

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • smtp.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • timo-vn.mail.protection.outlook.com

SPF policy

  • ip: 167.89.99.179/32
  • ip: 168.245.40.44/32
  • include: _spf.psm.knowbe4.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: _spf.samanage.com
  • include: servers.mcsv.net
  • include: mailgun.org
  • include: _spf_mkt.bizflycloud.vn
  • a: timo.vn
  • mx: timo.vn
  • ip: 18.140.167.8
  • ip: 18.142.26.43
  • ip: 210.245.17.202
  • ip: 54.254.33.120

Threat-feed evidence

History

Related pages

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