Skip to content

Hostname

cambridge.es

Last fetched

cambridge.es resolves to 94.23.80.13, announced in 94.23.0.0/16 by OVH - OVH SAS in FR. cambridge.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 · cambridge.esRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/cambridge.es

Resolution chain

IPv6 resolution

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

Attribution

ovh

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cambridge.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
220-server.cambridge.es
b2firstonline.cambridge.es
bilingualprogramme.cambridge.es
blog.cambridge.es
cambridgeencasa.cambridge.es
cambridgelabs.cambridge.es
cpanel.cambridge.es
cpcalendars.cambridge.es
cpcontacts.cambridge.es
csiberia.cambridge.es
curiosipics.cambridge.es
englishmonstruo.cambridge.es

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

  • ns5.cdmondns-01.com
  • ns1.cdmon.net
  • ns2.cdmon.net
  • ns3.cdmon.net
  • ns4.cdmondns-01.org

SPF policy

  • include: spf.profesionalhosting.com
  • ip: 94.23.80.13

Threat-feed evidence

History

Related pages

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