Skip to content

Hostname

mcp.es

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

sysadminok

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mcp.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
api-portalciudadania.mcp.es
buscador-pre.mcp.es
buscador-prod.mcp.es
buscador.mcp.es
correo.mcp.es
dev-api-portalciudadania.mcp.es
dev-login.mcp.es
dev-portalciudadania.mcp.es
ecoblog.mcp.es
extranet.mcp.es
fs.mcp.es
gestor-pre.mcp.es

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

  • dns1.serv513734.servidoresdns.net
  • dns2.serv513734.servidoresdns.net

MX records

  • mcp-es.mail.protection.outlook.com
  • mail.mcp.es
  • pruebamx.mcp.es

SPF policy

  • include: spf.acumbamail.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • a: mcp.es
  • mx: mcp.es
  • a: mail.mcp.es
  • a: smtp.mcp.es
  • ip: 195.76.209.196
  • ip: 31.47.76.171

Threat-feed evidence

History

Related pages

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