Skip to content

Hostname

volta.net.ar

Last fetched

volta.net.ar resolves to 179.43.114.162, announced in 179.43.114.0/24 by AS27823 - Dattatec.com in AR. volta.net.ar 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 · volta.net.arRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/volta.net.ar

Resolution chain

IPv6 resolution

No AAAA record for volta.net.ar is recorded in WhisperGraph.

Attribution

dattatec com

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for volta.net.ar. 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.volta.net.ar
cpanel.volta.net.ar
cpcalendars.volta.net.ar
cpcontacts.volta.net.ar
mail.volta.net.ar
webdisk.volta.net.ar
webmail.volta.net.ar
www.volta.net.ar

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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.dnscordobahosting.com
  • ns2.dnscordobahosting.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

MX records

  • volta.net.ar

SPF policy

  • a: volta.net.ar
  • mx: volta.net.ar
  • ip: 179.43.114.162

Threat-feed evidence

History

Related pages

Pivot from volta.net.ar 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: "volta.net.ar"})-[: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.