Skip to content

Hostname

roca.com.br

Last fetched

roca.com.br resolves to 45.33.62.53, announced in 45.33.32.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. roca.com.br 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 · roca.com.brRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.9/10canon.whisper.security/host/roca.com.br

Resolution chain

IPv6 resolution

No AAAA record for roca.com.br is recorded in WhisperGraph.

Attribution

akamai

ORIGIN_AS

WHOIS identity

Contact emails
roni@triader.com.br, luiz.benevenuto@gmail.com

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

  • dns1.moldsystems.com.br
  • dns2.moldsystems.com.br
  • dns3.moldsystems.com.br
  • dns4.moldsystems.com.br
  • 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
  • dns1.uni5.net
  • dns2.uni5.net
  • dns3.uni5.net
  • dns4.uni5.net

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
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.rdstation.com.br
  • a: roca.com.br
  • mx: roca.com.br
  • include: _spf.google.com
  • include: sendgrid.net
  • include: _spf.uni5.net

Threat-feed evidence

History

Related pages

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