Skip to content

Hostname

interpartner.com.br

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for interpartner.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
autodiscover.interpartner.com.br
mail.interpartner.com.br
mail2.interpartner.com.br
mail3.interpartner.com.br
mail4.interpartner.com.br
owa.interpartner.com.br
sip.interpartner.com.br

Showing 7 of 7 subdomains (7 per page).

Mail and authentication

Nameservers

  • ns1.markmonitor.com
  • ns2.markmonitor.com
  • ns3.markmonitor.com
  • ns4.markmonitor.com
  • ns5.markmonitor.com
  • ns6.markmonitor.com
  • ns7.markmonitor.com
  • 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

SPF policy

  • include: spf-00181c02.pphosted.com

Threat-feed evidence

History

Related pages

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