Skip to content

Hostname

uritec.es

Last fetched

uritec.es resolves to 31.47.78.103, announced in 31.47.72.0/21 by Tecnocratica - Tecnocratica Centro de Datos, S.L. in ES. uritec.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 · uritec.esRouting diversity1.5/10Peering density5.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/uritec.es

Resolution chain

IPv6 resolution

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

Attribution

tecnocratica centro de datos

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for uritec.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
beta.uritec.es
control.uritec.es
estadisticaswebs.uritec.es
generacionpdfs.uritec.es
ns7n.uritec.es
ns8.uritec.es
ns8n.uritec.es
panel.uritec.es
plesk01.uritec.es
plesk02.uritec.es
www.uritec.es

Showing 11 of 11 subdomains (11 per page).

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.neodigit.net
  • ns2.neodigit.net

MX records

  • bmx01.neodigit.net
  • bmx02.neodigit.net

SPF policy

  • a: uritec.es
  • mx: uritec.es
  • include: host0v1b26-a103.neodigit.net
  • ip: 185.49.184.31
  • ip: 31.47.76.171
  • ip: 31.47.76.39

Threat-feed evidence

History

Related pages

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