Skip to content

Hostname

electrolux.com.ar

Last fetched

electrolux.com.ar resolves to 104.126.37.138, announced in 104.126.36.0/23 by AKAMAI-ASN1 - Akamai International B.V. in DE. electrolux.com.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 · electrolux.com.arRouting diversity1.5/10Peering density9.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/electrolux.com.ar

Resolution chain

IPv6 resolution

Attribution

akamai international

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for electrolux.com.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
campusvirtual.electrolux.com.ar
cuida.electrolux.com.ar
gsqa-ho.electrolux.com.ar
gsqa.electrolux.com.ar
i.electrolux.com.ar
institucional.electrolux.com.ar
mail.electrolux.com.ar
mx2.electrolux.com.ar
mx3.electrolux.com.ar
partner.electrolux.com.ar
tienda.electrolux.com.ar
tiendaempleados.electrolux.com.ar

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

  • a1-199.akam.net
  • a10-64.akam.net
  • a11-65.akam.net
  • a2-66.akam.net
  • a3-67.akam.net
  • udns1.cscdns.net

MX records

  • mxa-00322602.gslb.pphosted.com
  • mxb-00322602.gslb.pphosted.com

SPF policy

  • include: %{ir}.%{v}.%{d}.spf.has.pphosted.com

Threat-feed evidence

History

Related pages

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