Skip to content

Hostname

prosoft.com.br

Last fetched

prosoft.com.br resolves to 170.82.173.10, announced in 170.82.172.0/23 by AS266444 - 3L CLOUD INTERNET SERVICES LTDA - EPP in BR. prosoft.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 · prosoft.com.brRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/prosoft.com.br

Resolution chain

IPv6 resolution

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

Attribution

3l ltda epp

ORIGIN_AS

WHOIS identity

Registrant organisation
alterdata tecnologia em informatica ltda.
Contact emails
compras.infra@alterdata.com.br, jean.quadrado@wolterskluwer.com.br

Subdomains

Subdomain
_spf.prosoft.com.br
arquivoscol.prosoft.com.br
auditor.prosoft.com.br
backoffice.prosoft.com.br
centralonline.prosoft.com.br
conteudo.prosoft.com.br
dev-esocialautorizacao.prosoft.com.br
devcol.prosoft.com.br
diagnostico1.prosoft.com.br
e-learning.prosoft.com.br
feedbackzon.prosoft.com.br
ftp1.prosoft.com.br

Showing 12 of 29. 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

  • damon.ns.cloudflare.com
  • roxy.ns.cloudflare.com

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.prosoft.com.br
  • include: _spf.rdstation.com.br
  • include: _spf.google.com
  • include: spf.protection.outlook.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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