Skip to content

Hostname

wetaca.com

Last fetched

wetaca.com resolves to 13.36.104.180, announced in 13.36.0.0/14 by AMAZON-02 - Amazon.com, Inc. in FR. wetaca.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 · wetaca.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/wetaca.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:379
Registrant organisation
andres casal goicoechea
Contact emails
andrescasal1989@hotmail.com, whoiscontact@domainconnection.info

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-90.awsdns-11.com
  • ns-1002.awsdns-61.net
  • ns-1376.awsdns-44.org
  • ns-1915.awsdns-47.co.uk

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: 52.128.40.0/21
  • ip: 217.8.118.0/24
  • ip: 154.53.134.0/24
  • ip: 173.236.20.0/24
  • ip: 103.229.233.0/24
  • ip: 192.92.97.0/24
  • ip: 79.99.129.0/25
  • ip: 212.63.110.178/31
  • include: amazonses.com
  • include: _netblocks.google.com
  • include: _netblocks2.google.com
  • include: _netblocks3.google.com
  • a: a1.profesionalhosting.com
  • a: a2.profesionalhosting.com
  • a: a3.profesionalhosting.com
  • a: a4.profesionalhosting.com
  • include: mail.zendesk.com
  • ip: 212.63.110.140
  • ip: 89.46.90.96

Threat-feed evidence

History

Related pages

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