Skip to content

Hostname

electronow.es

Last fetched

electronow.es resolves to 93.189.88.30, announced in 93.189.88.0/24 by CLOUDING - CLOUDI NEXTGEN SL in ES. electronow.es 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 · electronow.esRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/electronow.es

Resolution chain

IPv6 resolution

No AAAA record for electronow.es is recorded in WhisperGraph.

Attribution

cloudi nextgen

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for electronow.es. 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
apien.electronow.es
apien2.electronow.es
blog.electronow.es
chat-bot.electronow.es
img.electronow.es
panel.electronow.es
pruebas.electronow.es
static.electronow.es
www.electronow.es

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

  • ns3.interdomain.es
  • ns1.interdomain.net
  • ns2.interdomain.net

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.google.com
  • a: electronow.es
  • mx: electronow.es

Threat-feed evidence

History

Related pages

Pivot from electronow.es 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: "electronow.es"})-[: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.