Skip to content

Hostname

pacojetbr.com.br

Last fetched

pacojetbr.com.br resolves to 187.101.1.182, announced in 187.101.0.0/16 by AS27699 - TELEFONICA BRASIL S.A in BR. pacojetbr.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 · pacojetbr.com.brRouting diversity2.4/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/pacojetbr.com.br

Resolution chain

IPv6 resolution

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

Attribution

telefã nica brasil

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for pacojetbr.com.br. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
active.pacojetbr.com.br
autoconfig.pacojetbr.com.br
autodiscover.pacojetbr.com.br
imap.pacojetbr.com.br
mail.pacojetbr.com.br
ns1.pacojetbr.com.br
smtp.pacojetbr.com.br
webmail.pacojetbr.com.br

Showing 8 of 8 subdomains (8 per page).

Mail and authentication

Nameservers

  • ns1.pacojetbr.com.br
  • ns1.cold.srv.br
  • zuloo.cold.srv.br
  • zuloo1.cold.srv.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

MX records

  • loop3.edgc.com.br

SPF policy

  • a: loop3.edgc.com.br
  • mx: loop3.edgc.com.br
  • mx: ns1.pacojetbr.com.br
  • ip: 187.101.1.182
  • ip: 201.192.97.62
  • ip: 201.6.245.169

Threat-feed evidence

History

Related pages

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