Skip to content

Hostname

frete.com

Last fetched

frete.com resolves to 161.132.11.18, announced in 161.132.11.0/24 by AS3132 - Red Cientifica Peruana in PE. frete.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 · frete.comRouting diversity2.4/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/frete.com

Resolution chain

IPv6 resolution

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

Attribution

red cientifica peruana

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
braslink network
Contact emails
fabio@braslink.com

Subdomains

Subdomain
contratos-kmm.frete.com
crm-zoho.frete.com
cyber.frete.com
dev-cyberai.frete.com
estagio.frete.com
fuel.frete.com
keycloak-cyber.frete.com
nodered-cyber.frete.com
rancher-cyber.frete.com
shuffle.frete.com
wazuh.frete.com
www.frete.com

Showing 12 of 13. View all subdomains →

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

  • a1-99.akam.net
  • a11-67.akam.net
  • a13-64.akam.net
  • a22-67.akam.net
  • a6-67.akam.net
  • a8-67.akam.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

SPF policy

  • include: _spf.google.com
  • include: one.zoho.com
  • include: _spf.qp-mail.mx
  • include: 9020753.spf04.hubspotemail.net

Threat-feed evidence

History

Related pages

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