Skip to content

Hostname

prodeb.gov.br

Last fetched

prodeb.gov.br resolves to 200.187.60.34, announced in 200.187.32.0/19 by AS25832 - Cia. de Processamento de Dados do Estado da Bahia in BR. prodeb.gov.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 · prodeb.gov.brRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/prodeb.gov.br

Resolution chain

IPv6 resolution

No AAAA record for prodeb.gov.br is recorded in WhisperGraph.

Attribution

cia de processamento dados do estado da bahia

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for prodeb.gov.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
biponline.prodeb.gov.br
cpu0020.prodeb.gov.br
ftp.prodeb.gov.br
media.prodeb.gov.br
www.prodeb.gov.br

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

Mail and authentication

Nameservers

  • cpu0034.ba.gov.br
  • cpu0020.prodeb.gov.br
  • ns1.pop-ba.rnp.br
  • ns2.pop-ba.rnp.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

  • prodeb-gov-br.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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