Skip to content

Hostname

segorbe.es

Last fetched

segorbe.es resolves to 82.194.68.56, announced in 82.194.64.0/20 by acens_AS - acens Technologies, S.L. in ES. segorbe.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 · segorbe.esRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/segorbe.es

Resolution chain

IPv6 resolution

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

Attribution

acens

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for segorbe.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
actualidad.segorbe.es
audiovisualhistorico.segorbe.es
ayuntamiento.segorbe.es
biblioteca.segorbe.es
carpeta.segorbe.es
centrocultural.segorbe.es
conservatorio.segorbe.es
correo.segorbe.es
decide.segorbe.es
deportes.segorbe.es
edificioglorieta.segorbe.es
entradas.segorbe.es

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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.entorno.com
  • ns2.entorno.com
  • ns3.entorno.com
  • ns4.entorno.com
  • conex.dipcas.es
  • pluton.dipcas.es

MX records

  • mx.segorbe.es

SPF policy

  • mx: segorbe.es
  • a: correo.segorbe.es
  • a: smtp.segorbe.es
  • a: www.segorbe.es
  • include: spf.dominioabsoluto.net

Threat-feed evidence

History

Related pages

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