Hostname
controlnet.es
Last fetched
controlnet.es resolves to 34.175.232.129, announced in 34.175.128.0/17 by GOOGLE-CLOUD-PLATFORM - Google LLC in ES. controlnet.es is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 34.175.232.129
34.175.128.0/17 · GOOGLE-CLOUD-PLATFORM - Google LLC · Madrid, ES
IPv6 resolution
No AAAA record for controlnet.es is recorded in WhisperGraph.
Attribution
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for controlnet.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
- ns-43-b.gandi.net
- ns-6-a.gandi.net
- ns-99-c.gandi.net
- ns1.gandi.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
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
- aspmx4.googlemail.com
- aspmx5.googlemail.com
- envios.controlnet.es.controlnet.es
- ms47594835.msv1.invalid.controlnet.es
SPF policy
- include: _spf.google.com
- include: spf.sendinblue.com
- include: _spf.smtp.com
- mx: controlnet.es
Threat-feed evidence
History
Related pages
Pivot from controlnet.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: "controlnet.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.