Skip to content

Hostname

teror.es

Last fetched

teror.es resolves to 82.98.131.121, announced in 82.98.128.0/18 by DINAHOSTING-AS - DinaHosting S.L. in ES. teror.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 · teror.esRouting diversity1.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/teror.es

Resolution chain

IPv6 resolution

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

Attribution

dinahosting

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for teror.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
auditorio.teror.es
cv.teror.es
esquelas.teror.es
eventos.teror.es
fiestadelpino.teror.es
juventud.teror.es
padron.teror.es
radioteror.teror.es
reservas.teror.es
rutas.teror.es
transparencia.teror.es
turismo.teror.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

  • ns.dinahosting.com
  • ns.gestiondecuenta.com
  • ns2.gestiondecuenta.com

MX records

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

SPF policy

  • ip: 213.99.29.168/29
  • ip: 213.4.82.192/26
  • include: _flatsvcs.espublico.com
  • include: _spf.espublico.com
  • include: spf.protection.outlook.com
  • ip: 213.99.29.169
  • ip: 82.98.131.121
  • ip: 82.98.134.240

Threat-feed evidence

History

Related pages

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