Hostname
wal.com.sa
Last fetched
wal.com.sa resolves to 162.159.136.54, announced in 162.159.128.0/19 by CLOUDFLARENET - Cloudflare, Inc. in CA. wal.com.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
- 162.159.136.54
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 162.159.137.54
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for wal.com.sa is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for wal.com.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
| Subdomain |
|---|
| lms.wal.com.sa |
| www.wal.com.sa |
Showing 2 of 2 subdomains (2 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.
Sample inbound links
- alfa.seo-anomaly-cairo.online
- alfa.seo-anomaly-delhi.online
- alfa.seo-anomaly-guangzhou.online
- alfa.seo-anomaly-karachi.online
- alfa.seo-anomaly-kolkata.online
- alfa.seo-anomaly-lahore.online
- alfa.seo-anomaly-mexico.online
- alfa.seo-anomaly-moscow.online
- alfa.seo-anomaly-osaka.online
- alfa.seo-anomaly-sao-paulo.online
Mail and authentication
Nameservers
- paloma.ns.cloudflare.com
- titan.ns.cloudflare.com
- ns10.dnetns.com
- ns11.dnetns.com
MX records
- mx1.emailsrvr.com
- mx2.emailsrvr.com
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.elasticemail.com
- include: emailsrvr.com
- a: wal.com.sa
- mx: wal.com.sa
Threat-feed evidence
History
Related pages
Pivot from wal.com.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: "wal.com.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.