Hostname
cardial.sa
Last fetched
cardial.sa resolves to 104.21.44.13, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. cardial.sa 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.21.44.13
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.192.204
172.67.192.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 91.209.253.12
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.13
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.14
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.9
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.10
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.11
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 162.159.143.27
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.3.23
172.66.0.0/22 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cardial.sa. 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
Showing 3 of 3 subdomains (3 per page).
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
- donald.ns.cloudflare.com
- leia.ns.cloudflare.com
MX records
- smtp.google.com
Threat-feed evidence
History
Related pages
Pivot from cardial.sa 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: "cardial.sa"})-[: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.