Skip to content

Hostname

march.es

Last fetched

march.es resolves to 185.246.52.107, announced in 185.246.52.0/24 by SysAdminOK - SysAdminOK SL in ES. march.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 · march.esRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/march.es

Resolution chain

IPv6 resolution

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

Attribution

sysadminok

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for march.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
abnopac.march.es
accesowifi.march.es
apps.march.es
archivesspace.march.es
archivo.march.es
bigdata.march.es
canal-pre-static.march.es
canal-pre.march.es
canal-pro24.march.es
canal.march.es
catalogo.march.es
cdndigital.march.es

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

Mail and authentication

Nameservers

  • ns1-06.azure-dns.com
  • ns4-06.azure-dns.info
  • ns2-06.azure-dns.net
  • ns3-06.azure-dns.org

MX records

  • march-es.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: sendgrid.net
  • include: u2076852.wl.sendgrid.net
  • ip: 198.21.0.125

Threat-feed evidence

History

Related pages

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