Skip to content

Hostname

condor.es

Last fetched

condor.es resolves to 104.21.81.232, announced in 104.22.25.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. condor.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 · condor.esRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/condor.es

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for condor.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
account.condor.es
boletin.condor.es
extranet.condor.es
extranetb2b.condor.es
forms.condor.es
info.condor.es
mail.condor.es
marketing.condor.es
newsletter.condor.es
shop.condor.es
www.condor.es

Showing 11 of 19. 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

  • dolly.ns.cloudflare.com
  • trey.ns.cloudflare.com

MX records

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

SPF policy

  • ip: 88.99.99.172/32
  • ip: 217.149.4.176/32
  • ip: 78.46.46.208/32
  • ip: 213.97.31.218/32
  • ip: 92.243.18.219/32
  • ip: 217.113.245.6/32
  • include: spf.a3asesor-rrhh.com
  • include: condor.ip-zone.com
  • include: spf.protection.outlook.com
  • a: condor.es
  • mx: condor.es
  • include: servers.mcsv.net
  • include: eu.zcsend.net

Threat-feed evidence

History

Related pages

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