Hostname
consum.es
Last fetched
consum.es resolves to 45.60.34.23, announced in 45.60.36.0/24 by INCAPSULA - Incapsula Inc in GB. consum.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
- 45.60.34.23
45.60.36.0/24 · INCAPSULA - Incapsula Inc · London, GB
- 45.60.40.23
45.60.44.0/24 · INCAPSULA - Incapsula Inc · London, GB
IPv6 resolution
No AAAA record for consum.es is recorded in WhisperGraph.
Attribution
incapsula
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for consum.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.
Sample inbound links
Mail and authentication
Nameservers
- ns0.s2grupo.com
- ns1.s2grupo.com
- ns4.s2grupo.com
- 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
- mx.consum.es
- d341248.a.ess.de.barracudanetworks.com
- d341248.b.ess.de.barracudanetworks.com
SPF policy
- ip: 195.76.59.192/26
- ip: 77.226.150.96/27
- include: _spf.kmitd.com
- include: spf.protection.outlook.com
- mx: consum.es
- a: mx.consum.es
- include: spf.emailingemfasis.es
- include: _spf-dc55.sapsf.eu
- ip: 185.215.84.14
- ip: 185.215.84.31
- ip: 185.215.84.53
- ip: 185.215.85.53
- ip: 195.76.59.202
Threat-feed evidence
History
Related pages
Pivot from consum.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: "consum.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.