Skip to content

Hostname

gaca.gov.sa

Last fetched

gaca.gov.sa resolves to 66.9.137.21, announced in 66.9.137.0/24 by NIC-SDAIA-Deem - NIC (National Information Center)- SDAIA ( Saudi Data and Artificial Intelligence Authority ) in SA. gaca.gov.sa is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · gaca.gov.saRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/gaca.gov.sa

Resolution chain

IPv6 resolution

Attribution

nic national information center sdaia saudi artificial intelligence authority

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for gaca.gov.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
access.gaca.gov.sa
api.gaca.gov.sa
assist.gaca.gov.sa
at-sahab.gaca.gov.sa
careers.gaca.gov.sa
cert.gaca.gov.sa
eservices.gaca.gov.sa
etsc2uat.gaca.gov.sa
ghq-expe-01.gaca.gov.sa
ghq-expe-02.gaca.gov.sa
jcms01.gaca.gov.sa
meeting.gaca.gov.sa

Showing 12 of 28. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.gaca.gov.sa
  • ns2.gaca.gov.sa

MX records

  • mx1.deem.sa
  • mx2.deem.sa
  • mx3.deem.sa
  • mx4.deem.sa

SPF policy

  • include: smtps03.detasad.com
  • include: unismtp.detasad.com
  • mx: gaca.gov.sa
  • ip: 185.131.97.20
  • ip: 185.131.97.21
  • ip: 195.170.180.131
  • ip: 195.170.180.132

Threat-feed evidence

History

Related pages

Pivot from gaca.gov.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: "gaca.gov.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.