Skip to content

Hostname

servytec.es

Last fetched

servytec.es resolves to 213.172.39.18, announced in 213.172.32.0/19 by AS15704 - XTRA TELECOM S.A. in ES. servytec.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 · servytec.esRouting diversity1.5/10Peering density6.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/servytec.es

Resolution chain

IPv6 resolution

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

Attribution

xtra

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for servytec.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
anubis.servytec.es
arges.servytec.es
atenea.servytec.es
aura.servytec.es
belerofonte.servytec.es
freya.servytec.es
gaia.servytec.es
git.servytec.es
gluon.servytec.es
imap.servytec.es
loki.servytec.es
mail.servytec.es

Showing 12 of 32. 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.servytec.es
  • ns2.servytec.es
  • ns3.servytec.es
  • ns4.servytec.es
  • ns5.servytec.es
  • ns6.servytec.es

MX records

  • imap.servytec.es
  • loki.servytec.es
  • mail.servytec.es
  • pop3.servytec.es
  • smtp.servytec.es
  • smtp002.servytec.es

SPF policy

  • ip: 212.230.121.144/28
  • ip: 193.163.93.151/32
  • ip: 213.172.39.16/28
  • ip: 2a11:1f40::/29
  • ip: 2a11:1f40::/32
  • ip: 217.172.77.96/27

Threat-feed evidence

History

Related pages

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