Skip to content

Hostname

wikanda.es

Last fetched

wikanda.es resolves to 217.12.31.100, announced in 217.12.31.0/24 by JJAA-AS - Sociedad Andaluza para el Desarrollo de las Telecomunicaciones S.A. Medio Propio in ES. wikanda.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 · wikanda.esRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/wikanda.es

Resolution chain

IPv6 resolution

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

Attribution

sociedad andaluza para el desarrollo de las telecomunicaciones medio propio

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for wikanda.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
almeriapedia.wikanda.es
archivos.wikanda.es
cadizpedia.wikanda.es
cordobapedia.wikanda.es
dumps.wikanda.es
granadapedia.wikanda.es
huelvapedia.wikanda.es
jaenpedia.wikanda.es
malagapedia.wikanda.es
sevillapedia.wikanda.es
www.wikanda.es

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

  • ns.juntadeandalucia.es
  • ns1.juntadeandalucia.es
  • ns3.juntadeandalucia.es
  • ns4.juntadeandalucia.es

MX records

  • mx.juntadeandalucia.es
  • mx2.juntadeandalucia.es

Threat-feed evidence

History

Related pages

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