Skip to content

Hostname

fcta.es

Last fetched

fcta.es resolves to 96.45.82.112, announced in 96.45.82.0/24 by DIGICERT - Tiggee LLC in US. fcta.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 · fcta.esRouting diversity2.4/10Peering density7.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint9.7/10canon.whisper.security/host/fcta.es

Resolution chain

IPv6 resolution

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

Attribution

tiggee

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fcta.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

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • elisabeth.ns.cloudflare.com
  • louis.ns.cloudflare.com
  • ns20.digicertdns.com
  • ns21.digicertdns.com
  • ns22.digicertdns.com
  • ns10.dnsmadeeasy.com
  • ns1.sport2fit.com
  • ns2.sport2fit.com
  • ns3.sport2fit.com
  • ns4.sport2fit.com
  • ns5.sport2fit.com
  • ns6.sport2fit.com
  • ns23.digicertdns.net
  • ns24.digicertdns.net
  • ns25.digicertdns.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • mail.fcta.es
  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net

Threat-feed evidence

History

Related pages

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