Skip to content

Hostname

tecazuay.edu.ec

Last fetched

tecazuay.edu.ec resolves to 135.181.112.62, announced in 135.181.0.0/16 by HETZNER-AS - Hetzner Online GmbH in FI. tecazuay.edu.ec 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 · tecazuay.edu.ecRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/tecazuay.edu.ec

Resolution chain

IPv6 resolution

No AAAA record for tecazuay.edu.ec is recorded in WhisperGraph.

Attribution

hetzner

ORIGIN_AS

WHOIS identity

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

  • ns1.kapchosting.com
  • ns2.kapchosting.com
  • ns1.kapcservice.com
  • ns2.kapcservice.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 209.85.128.180/9
  • include: _spf.google.com
  • a: tecazuay.edu.ec
  • mx: tecazuay.edu.ec
  • include: relay.mailchannels.net
  • ip: 135.181.112.62
  • ip: 138.197.77.108
  • ip: 149.255.59.14
  • ip: 149.255.59.51
  • ip: 195.201.106.177
  • ip: 198.136.62.200
  • ip: 205.234.134.36
  • ip: 50.31.177.178
  • ip: 65.108.69.93
  • ip: 65.109.154.218
  • ip: 65.109.154.253
  • ip: 65.109.83.31
  • ip: 65.109.83.50
  • ip: 65.109.83.57
  • ip: 77.72.0.142

Threat-feed evidence

History

Related pages

Pivot from tecazuay.edu.ec 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: "tecazuay.edu.ec"})-[: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.