Hostname
ente.com
Last fetched
ente.com resolves to 104.18.2.158, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ente.com 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
- 104.18.2.158
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.3.158
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.20.39.25
104.20.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.5.97
104.21.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.152.229
172.66.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.133.68
172.67.128.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 185.66.41.58
185.66.40.0/22 · CDmon - 10dencehispahard, S.L. · Malgrat de Mar, ES
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1403
- Registrant organisation
- ente publicidad,
- Contact emails
- jorge@ente.com
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
- ns5.cdmondns-01.com
- henry.ns.cloudflare.com
- jade.ns.cloudflare.com
- ns1.cdmon.net
- ns2.cdmon.net
- ns3.cdmon.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
- ns4.cdmondns-01.org
MX records
- correo.emaillimpio.com
- srvmail.ente.com
- ente-com.mail.protection.outlook.com
- mx.zoho.com
- mx2.zoho.com
- mx3.zoho.com
SPF policy
- include: _spf.srv.cat
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from ente.com 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: "ente.com"})-[: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.