Hostname
electropar.com.py
Last fetched
electropar.com.py resolves to 35.247.213.253, announced in 35.247.208.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in BR. electropar.com.py is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 35.247.213.253
35.247.208.0/20 · GOOGLE-CLOUD-PLATFORM - Google LLC · São Paulo, BR
IPv6 resolution
No AAAA record for electropar.com.py is recorded in WhisperGraph.
Attribution
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for electropar.com.py. 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 |
|---|
| imap.electropar.com.py |
| ksmg.electropar.com.py |
| mail.electropar.com.py |
| mail2.electropar.com.py |
| www.electropar.com.py |
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.
Mail and authentication
Nameservers
- ns1-03.azure-dns.com
- ns1-07.azure-dns.com
- ns4-03.azure-dns.info
- ns4-07.azure-dns.info
- ns2-03.azure-dns.net
- ns2-07.azure-dns.net
- ns3-03.azure-dns.org
- ns3-07.azure-dns.org
MX records
- ksmg.electropar.com.py
- mail.electropar.com.py
- mail2.electropar.com.py
SPF policy
- include: spf.dattamax.com
- include: spf.protection.outlook.com
- include: spf.zoho.com
- include: transmail.net
- include: zcsend.net
- mx: electropar.com.py
- a: ksmg.electropar.com.py
- a: mail.electropar.com.py
- a: mail2.electropar.com.py
- ip: 131.161.252.72
- ip: 190.128.235.42
- ip: 190.211.243.154
Threat-feed evidence
History
Related pages
Pivot from electropar.com.py 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: "electropar.com.py"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.