Skip to content

Hostname

owoko.com.ar

Last fetched

owoko.com.ar resolves to 185.133.35.13, announced in 185.133.35.0/24 by AS273584 - LINKED STORE BRASIL CRIACAO E DESENVOL DE SOFTWARE in BR. owoko.com.ar 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 · owoko.com.arRouting diversity2.4/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.5/10canon.whisper.security/host/owoko.com.ar

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrant organisation
ipv4 address block not managed by the ripe ncc

Subdomains

Subdomain
cpanel.owoko.com.ar
mail.owoko.com.ar
tienda.owoko.com.ar
webdisk.owoko.com.ar
webmail.owoko.com.ar
www.owoko.com.ar

Showing 6 of 6 subdomains (6 per page).

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

  • heather.ns.cloudflare.com
  • lennox.ns.cloudflare.com
  • ns1.towebs.com
  • ns2.towebs.com
  • ns3.towebs.com
  • 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

MX records

  • mail.owoko.com.ar
  • mx.zoho.com
  • mx2.zoho.com
  • mx3.zoho.com

SPF policy

  • a: owoko.com.ar
  • mx: owoko.com.ar
  • include: spf.fromdoppler.com
  • ip: 181.119.48.196
  • ip: 190.61.219.123
  • ip: 190.61.219.133
  • ip: 190.61.219.198
  • ip: 190.61.219.77
  • ip: 190.61.250.160
  • ip: 200.80.43.223

Threat-feed evidence

History

Related pages

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