Skip to content

Hostname

correamte.com.br

Last fetched

correamte.com.br resolves to 13.224.125.13, announced in 13.224.136.0/24 by AMAZON-02 - Amazon.com, Inc. in US. correamte.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 · correamte.com.brRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/correamte.com.br

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
corr?a materiais el?tricos ltda
Contact emails
suporte@correamte.com.br

Subdomains

Subdomain
click.correamte.com.br
mkt.correamte.com.br
www.correamte.com.br

Showing 3 of 3 subdomains (3 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

  • ns-93.awsdns-11.com
  • ns-792.awsdns-35.net
  • 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
  • ns-1173.awsdns-18.org
  • ns-2013.awsdns-59.co.uk

MX records

  • mx.a.locaweb.com.br
  • mx.b.locaweb.com.br
  • mx.core.locaweb.com.br
  • mx.jk.locaweb.com.br

SPF policy

  • a: correamte.com.br
  • mx: correamte.com.br
  • include: _spf.locaweb.com.br
  • include: _spf.kmitd.com

Threat-feed evidence

History

Related pages

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